(Solved)Updating broke my workaround :(
I was still on .5 version.
I needed to reorganize the layout of the fields in the person view page. To do this as a work around, I created the custom fields using letters before the actual title. So:
Title would be "aaTitle" when created. Then once renamed, it would keep the aaTitle name for the variable, but changing the name could display "Title".
I updated to 1.0.2. It seems the dev's have fixed this "bug".
Any other way someone has found to work around this until the devs implement an official method?
4 Replies
Hello, I haven't heard about a ordering update on these
Do you mean they're not alphabatically ordered anymore ?
The oposite actually. My work around made me be able to choose the order by "adding" letters infront when creating the field. Then removing the letters from being displayed (the variable name of the field remained the same as on creation, despite renaming the field).
This has been fixed. Now I'm wondering if there's any other workarounds anyone knows of since implementation isn't soon.
@Dream: Have you checked if the 'Synchronize Objects Labels and API Names' option has been turned on during the update?
You need to turn on Advanced options in the Admin panel, then look at the settings for your data models.
You. I love you.
Thank you