When adding a new persistent field into a Custom Logical Unit , I get the following error. Currently I'm having 36 attributes in the Custom LU. Customer is currently using Apps 10 Update 7.
Has anyone come across this and come to any solution?
Page 1 / 1
Hi @XitUviniG ,
Usually this error comes when there is an issue in the exisiting custom fields. Could you try disabling each and find the exact custom field which issue is coming from. Could i also know whether all the 36 custom attributes are created in App10 UPD 7 or is it migrated from a previous track. I have noticed similar errors for migrated custom attributes where there is a inconsistancy in current track/version.
Nilushi-
Hi @Nilushi Silva ,
I've tried disabling each field but that didn't fix the issue. This is due to the newly added field. Adding a new field to only this LU will give this error .This is not migrated from a previous track and this is only coming in one environment .(Same copy is available in Dev environment and this issue is does not exist there).
Uvini
Hi @XitUviniG,
Could you please share us some screen shots of the custom field configuration which you are newly adding and also could you please follow below steps and provide the screenshot generated objects.
(similar to above screenshot)
Nilushi -
Hi @Nilushi Silva ,
I've tried disabling each field but that didn't fix the issue. This is due to the newly added field. Adding a new field to only this LU will give this error .This is not migrated from a previous track and this is only coming in one environment .(Same copy is available in Dev environment and this issue is does not exist there).
Uvini
If it’s only happening in one environment, I recommend you refresh that environment from PROD and start over. This will save you time troubleshooting, but there’s a bigger issue at stake. Whatever is making that environment broken in this situation might also make other things work, and you want to be absolutely sure that whatever you develop there will still work when you deploy it to PROD.