Why is SDF trying to create the object while it al...
# sdfb
BS
10/19/2022, 10:46 AMWhy is SDF trying to create the object while it already exists? Why doesn't just update it instead?
a
Ali Syed (NS DevTools QA)
10/19/2022, 11:59 AMseems like custom object exists, but there is a new custom record custom field which is new, which its trying to create.
b
BS
10/19/2022, 12:49 PMThanks @Ali Syed (NS DevTools QA) so does it means that the custom record custom field id I would like to create already exists in an other custom record? And if so, is there a simple way via SuiteQL to search for the custom record which is using the same custom record custom field id?
BS
10/19/2022, 12:57 PMthis is the only explanation I can come up with for this error which is possible since people (Consultants) here are creating those objects in two different SB's via the UI.
BS
10/19/2022, 1:54 PMI had just tested and created a custom record custom field with the same script id and that works perfectly so there is no existing custom record custom field.
BS
10/19/2022, 1:54 PMStill I don't get why the deployment fails
a
Ali Syed (NS DevTools QA)
10/19/2022, 1:55 PMBut is it under same custom record?
Because the error was for fully qualified id.
b
BS
10/19/2022, 2:15 PMI had found the issue by using SuiteQL. An old custom record type which was created by a consultant had the same custom record custom field id.
BS
10/19/2022, 2:16 PMI again tried to create the custom record custom field manually and the UI threw a meaningful message
BS
10/19/2022, 2:17 PMwhich also appeared during the SDF deployment
BS
10/19/2022, 2:18 PMIt was the last row
BS
10/19/2022, 2:19 PMBut no, it was not the same custom record, it had a different id, while the name of the custom record type was the same!
BS
10/19/2022, 2:20 PMso a yes/no thing 😛
t
The Usual Suspect
10/19/2022, 5:22 PM@BS is this a suiteapp project?
The Usual Suspect
10/19/2022, 5:23 PMIf its a suiteapp project there is an app id you can expose via user preferences that you'll need to sync up on. My guess is that its in the account with no app id and your deployment is trying to add one WITH an app id and getting blocked
b
BS
10/20/2022, 9:13 AM@The Usual Suspect no this concerns a simple account customization project
BS
10/20/2022, 9:17 AMIn the end we need to set a procedure in place so that the consultants we hire aren't making duplicate object id's spread across different sandboxes . It's a bit unusual but we're making different features at the same time in separate sandboxes so the chance of using the same script id's is very likely.
3 Views