Hey! I had accidentally deployed my SuiteApp proje...
# suite-appi
Ivan Thai
06/27/2023, 7:28 PMHey! I had accidentally deployed my SuiteApp project via IDE to the account that owns the suiteapp without the Objects folder with the custom record type xml definitions. Netsuite thought I wanted to delete my objects/custom record types on deployment and went ahead and removed them. I then proceeded to add them back in and Netsuite recreated them with different internal ids. Now when users attempt to update their bundle, they will have to perform migrations of their Custom Records because the internalid have changed. Any advice? Thanks in advance!
watching following 1
f
fkrauthan
06/28/2023, 10:02 PMAre you sure about that? I thought the internal id does not matter but only the scriptid itself (which shouldn't have changed)?
i
Ivan Thai
06/29/2023, 1:02 AMThat’s what I thought too. I think the issue is not so much the conflict, but the fact that each object has a “Delete” action.
Ivan Thai
06/29/2023, 1:02 AMmessage has been deleted
Ivan Thai
06/29/2023, 1:03 AMThis is what users see when trying to upgrade. the objects were accidentally deleted and readded on the SuiteApp bundle distribution account
Ivan Thai
06/29/2023, 1:13 AMAccording to https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_N3394371.html#bridgehead_N3394425
It mentions that “*For any bundle object conflict where the Preview Bundle Update page displays both a Delete action, and a dropdown to select either Add and Rename, or Replace Existing Object, a bundle update causes deletion of the object and removal of its data from the target account.*” which is not desired
3 Views