Using suitebundler to create a customization bundl...
# suite-app
j
Using suitebundler to create a customization bundle. When I select custom forms to be included in the bundle, and then install the bundle into the target account, the forms don't mimic their setup from the account used to create the bundle. (Forms are being updated/overwritten in target account, rather than created.) I.e.: Printing Type remains "Basic" when it should be change to "Advanced", Field Groups not correctly assigned, many fields that should be hidden are visible, etc. Can't imagine this is normal behavior. Anyone have a clue?
z
I understand that is something you don't want in initial setup stage... but it is not only normal but from my point of view even required behavior! why? Imagine yuo are client which use that CUSTOM form and make some further customization... and arrive bundle updates and everything is reset... I don't want to reset any changes made by my client.. Yeah, I agree with you in advance : do not use forms fron bundle, instead of that always create copy/custom... maybe owner of bundle wants to change something 😁
j
I see what you mean! In my case I refreshed sandbox, built customization there, and then packaged via suitebundler for deployment back in prod. As you suggested, I just made changes to custom forms manually in prod instead of bundling those. Thanks for the reply
👍 1