Anybody have a workaround or solution for a custom...
# sdf
n
Anybody have a workaround or solution for a custom record that utilizes a saved search and the search also references the custom record. So, i can't deploy the record first because it needs the search and i can't deploy the search first because it needs the custom record. (This is in a suiteapp)
👀 1
s
Why not remove the search from the custom record definition in Ui, download new xml, deploy to target and re add manually?
Or vice Versa whichever requires least modifications
n
@SimonC If it were only a couple that would be fine, but we have several custom records and each has a search in it so it would be very time consuming
w
Have you tried to re-order them in the deploy.xml? Sometimes that does the trick when you're stuck.
n
Yeah, @Watz i have tried every which way i can think of.
s
I see your predicament. I mean if the custom records are similar in nature and require modifications in more or less the same spot I’ll be happy to provide you with a small script which will do the job
Feel free to dm
The other thing you might try is copy pasting the same dummy definition for a custom record or search and updating the scriptids to be the ones you need to deploy. Deploy these dummy objects so target account will have dependencies and then overwrite them with real ones later
Well you could even deploy them together as long as you would have deployed the placeholder objects first