Has anyone else using SDF and version control ever...
# sdf
s
Has anyone else using SDF and version control ever noticed that sometimes the position of certain elements is shifted when pulling a new copy of an object previously committed? Even though the object itself has not been modified inside the account.
a
like the xml nodes moving around? that doesn't actually change anything... but your version control shows them as changes? I've never seen that, sounds annoying
s
exactly, just the order not the actual content
a
does it KEEP happening on the same XML file? it might just be the case that when get latest account version it comes in a specific way? do you edit the xml by hand ever?
if its a one time thing per file, maybe that's no so annoying?
e
Yes. The order of the manifest file seems completely random
In the past I have gone so far as to write my own code that manually generates, updates, then sorts the manifest file on every release prep
🤯 2
x
Can't think of why you'd want to commit the manifest to the repo tbh it's more of a deployment artifact as I see it
e
It only becomes a deployment artifact if you have written code to generate it. Most teams I've advised or worked on haven't done that
I'm actually not sure how you don't commit the manifest if you haven't already built a generator for it
x
I tend to regard things like deploy.xml and manifest.xml as mere vehicles for deploying customizations to NetSuite rather than files that warrant versioning
e
How does a teammate deploy your SDF project after cloning it?
a
I think this got sidetracked, or I misunderstood? the orginal question was about NS OBJECT xml files.... not manifest.xml etc.
e
Either way, the XML nodes get rearranged, yes.
Never seen it happen in
deploy.xml
, but have seen it in all other XML files
I don't think any SDF commands modify
deploy.xml
though