This is due to the object order i assume but the C...
# sdf
k
This is due to the object order i assume but the Custom Record is First then the saved searches are afterwards but the custom record has a sublists for the saved searches
w
I'd like to know the definitive answer to this as well. The only way I can think of is to first deploy a version of the custom record without the sublist and then deploy the search. Then deploy the version with the sublist. Don't know if it would work though. Perhaps have three folders for objects: First, second and third. And then specify the order in deploy.xml?
k
I suppose you could have multiple versions of the same XML but then when you make a change you would have to edit both version or I suppose only include the extras on the second run.
Lot of manual xml changes though 😂
w
Yeah, not an optimal solution.
s
IMHO, one of the main reasons SDF
deploy
command exists is to work out those dependencies and get it right for the developer.
I think it's supposed to work out order of install but it just doesn't do a very thorough job of it
k
Would be lovely if it did. The interlinked objects obviously don’t like each other though.
a
Whats your deploy.xml look like? Does it include manual references for objects in <object> tag?
k
Hi @Ali Syed (NS DevTools QA), my deploy fully includes all the auto generated objects and features including one that doesn't even exist in the account which I have had to comment out
a
Can you share a screenshot of manifest via DM?