Number value is missing on new record creation

masella · ‎06-22-2015

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

masella · ‎07-13-2015

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.

View solution in original post

Pradeep Sharma · ‎06-22-2015

Hi Anthony,

Is the same issue reported on dev too. Please confirm.

masella · ‎06-22-2015

Hi Pradeep,

There is no issue in the development environment which is what makes this odd.

I haven't seen an issue like this is in the past.

bernyalvarado · ‎06-22-2015

Hi Anthony, it sounds like you have data corrupted on that table. Can you delete the 3 records and create a new one to see if the new one comes up with a valid number?

Just in case it helps, i believe the number creation is driven by the logic in the script include NumberManager

Thanks,

Berny

masella · ‎06-22-2015

Hi Berny,

Thanks for your advice, however that does not resolve.

I have looked at the script includes and all is consistent with Dev.