- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-22-2015 11:01 PM
Hi All,
Today I moved an ordinary update set from dev to test and found in the test environment when i created a new record that the number was not being allocated.
All appears to be fine from a number maintenance perspective, and I have checked that this issue doesn't occur on other task tables.
Any ideas on what could have caused this issue and steps to resolve?
Thanks in advance
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-13-2015 03:52 AM
Hi All,
So an update on this one, even though the following were both checked.
a) use dynamic default is checked
b) Dynamic Default value is set to Get Next Padded Number
When I went to the dictionary record from a list view the default value was actually missing which contradicts what I was seeing when looking at the dynamic default value. The fix was to add javascript:getNextObjNumberPadded(); as the default value.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-13-2015 03:52 AM
Hi All,
So an update on this one, even though the following were both checked.
a) use dynamic default is checked
b) Dynamic Default value is set to Get Next Padded Number
When I went to the dictionary record from a list view the default value was actually missing which contradicts what I was seeing when looking at the dynamic default value. The fix was to add javascript:getNextObjNumberPadded(); as the default value.