Hi all,
Created a new ItemType. Initially, when viewing an instance, Views > Revisions displays the Item Versions. However, after creating a few items, it then appears blank, as illustrated here:
I haven't changed anything (as far as I know), it just stops rendering after some time. Any input would be greatly appreciated.
Aras Version 11 SP9.
Thanks very much.
First try the classic approaches
1. Try in-private windows / clear cache
2. Check browser debugger for sus error messages
3. Reset your preferences in Innovator
Second:
Some time ago you asked why your revision dialog is so small.
It seems that the size of your dialog improved. Did you play around with revisionDialog.html?
Does the dialog work for other ItemTypes, like Methods or Parts?
Third:
Maybe some of your properties break the dialog. Not that I ever faced this scenario, but revision dialog relies on a few properties to be "there". Have you deleted some of the default properties?
Hi Angela, thanks for your reply.
1. I've tried most of these, except for resetting preferences. How do you do that? Can that be done within the user interface?
2. You have a great memory. I made the dialog larger by making the default widths for the containing properties larger, as per your suggestion.
3. Now that you mention it, I did rename the labels for "generation" and "major_rev" properties. I have changed them back but dialog still appearing empty.
1. In I12 you can reset the internal Innovator preferences in the menu in the top right corner. I don´t remember where these buttons were in I11 (so much for "great memory"). But look for the menu that also contains the Aras help and the license activation stuff.
2. Happy to hear that the "width" trick worked!
3. You definitely can rename the labels – no problem! Just don´t delete system properties like major_rev or generation. Aras should prevent that users delete these fields anyway. But I11 in particular has only minor sense of self-preservation.
Does the revision dialog still work for Methods and Parts?
Try to hide your custom fields to see if one of them cause the issue.
