I was trying to convert a managed bundle to a suiteapp. I tried the following approach. Added suiteapp id in all objects. Created a suitecloud suiteapp project and downloaded all objects locally. Installed the bundle in one test account. Used suitecloud to install the local project in the test account. My. assumption is that suitecloud is the same as suiteapp control center. Noticed 2 things. • Installation failed with An object with script ID dfgd already exists • The app id was automatically stripped when installing the bundle. Anyone has any idea how to overcome this? Or even if its possible or not

That first issue occurred for me when the script record was missing app id on the UI. Added that to the record and I was able to deploy again.

are you trying to deprecate the bundle and move to the suiteapp structure? I wasn't aware, you are able to do this yet? If so please let me know how!

I am not sure if you can. I will resume testing on Monday.

Yeah. I didn't think you can yet. It's a huge problem. I've always failed with the error Installation failed with An object with script ID dfgd already exists

Yes but if you add the app id then this error goes away. Netsuite is stripping the app id when you do a bundle installation. Any idea what is this behaviour ?

ahh i'll have to try it out. Have you seen any documentation on this?

Nope 🙂

are you adding the bundle id to the suiteapp?

Also no

Are you connecting the bundle to the app in anyway or expecting the app to sort of merge with the bundle?

Only by app id.

What do you mean by added app id on all objects in dev account?

The last step gave me the same error as yours but I noticed that app id is stripped from my qa account. Next week I asked implementation team to stop installing the app to clients for some time. The plan is to unlock objects in the bundle and install the bundle one more time. Then in the qa account I will just fill the app id. Main goal is to test behaviour after the error that you are getting as well.

are you adding it to the internal id of the object?

message has been deleted

hmmm. what record type are you on? i'm not seeing that in my account

go to user preferences and enable the option there

okay thanks!. so the idea is if we attach the suiteapp id on the custom record that is in the bundle, it will be able to be connected to the suiteapp when installed?

Yes.

okay. Thank you so much! We'll test this soon

Please tell me if you made a break through.

will do!

Any idea why they are blank ?

maybe the bundler does not intend to set the app and publisher id?

Do you know of any other way to set it? Like with a bundle installation script?

i'm not aware of being able to set id fields with such a thing. You could always open a support case

Yes I can confirm the above from my side as well

Yeah I noticed the exact same thing. It needs to check to see if the records were installed with a bundle and if so, honor the suiteapp settings to preserve instances that were deployed with the bundle and suiteapp and then remove the connection to the bundle

From here on I think I need to wait for netsuite support. I have no idea how to do any of the above. At least now I am confident that no instances will be deleted

yeah i'm with you. have you tested to see if someone created a custom form or field on a record and know if it was deleted?

Nope I did not think of it. I expect not to be a problem since both are tied to a script id

We have a couple of BFN SuiteApps which are deployed using managed bundles. We are trying to migrate to SDF with the intention of using the SuiteApp Control Centre (same as @Kyriakos Zisopoulos). Our expectation was that we should be able to: 1. Add the App Id to all objects in the source account 2. Push a bundle update to populate the App Id on the objects in the target accounts 3. Abandon the legacy bundle and start using the SDF deployment mechanisms (e.g. SuiteApp Control Centre). However, step 2 is unsuccessful. The App Ids are not populated in the target account when we push the managed bundle to the target accounts. This appears to be the only obstacle holding us back. If we can get the App Id in the target accounts then we are happy to abandon the legacy bundle (leave it installed) and then manage all updates going forward using SDF. It is not practical for us to manually update the target accounts because we have hundreds of objects, hundreds of customers and we don't have access to all of our customer accounts. We have an open defect regarding this: Defect 660145: SDF > SDN Trailing account > Populate App Id on existing objects in target accounts I encourage anyone who is suffering from the same issue to log a support case and reference the defect. Maybe we will get some traction. 🤞

No it’s not a hard requirement. Just a nice to have to have a clean system. I will just have to be prepared for arguments of the type: “What if someone thinks that the suiteapp is installed and un installs the bundle?”

I'm thinking we could add a check to the Bundle install script beforeUninstall function and prevent the uninstall if we detect that the SDF SuiteApp is installed. I've never used beforeUninstall, but I presume throwing an error would prevent the bundle from uninstalling.

Yes that looks like a good solution