Custom Properties - SOLVED
- Thread starter JimCad
- Start date
Hi Jim, my guess would be that the APPLY BUTTON never gets activated. If that is the case, click with your mouse on one of the custom property name and not the text field, then the apply button will activate, click on that and you should be good to go. Save your work and you're done.
Have a nice day,
The ENTER key on your keyboard will also work once you filled all the text fields, no apply button needed there. Then save your work.
I'll keep this short.
THIS IS SOLVED.
Been on a screen share with David J.
He noted that I had put a colon after my custom property names. eg Coating:
I removed the colons and it works.
DO NOT USE SPECIAL CHARACTERS in CUSTOM PROPERTY NAMES.
Thank you so much David.
And thank you to all who "chipped in" to try and help.
What a great forum & great software.
Jim
THIS IS SOLVED.
Been on a screen share with David J.
He noted that I had put a colon after my custom property names. eg Coating:
I removed the colons and it works.
DO NOT USE SPECIAL CHARACTERS in CUSTOM PROPERTY NAMES.
Thank you so much David.
And thank you to all who "chipped in" to try and help.
What a great forum & great software.
Jim
simonb65
Alibre Super User
This needs to be raised as a bug or enhancement. i.e. Alibre should warn you if you enter illegal characters or even remove them all together. It would make it easier than the user second guessing what is and what isn't allowed. I guess the developers 'assumed' that the user would never use special characters rather than validating the property name when it was created!
UPDATE: some testing suggests that the issue may be limited specifically to the colon character, some other special characters don't have the same issue. Not only does the property value 'not stick', the property definition doesn't transfer to other systems if the file is shared.
This has been passed to QA/Development for more detailed investigation - once the reason for the problem is found, they should be in better position to predict if any other characters could cause the same issues. The best way to address this can then be decided.
This has been passed to QA/Development for more detailed investigation - once the reason for the problem is found, they should be in better position to predict if any other characters could cause the same issues. The best way to address this can then be decided.
