How do you manage a client/customers account? Acco...
# suitescript
n
How do you manage a client/customers account? Account Customization SuiteApp? Folder structure? GIT? Combo?
a
I think only suiteapps would use a suiteapp, so that would mean account customization for individual customers folder structure for code, i think depends on how many scripts they have, I've seen everything just get dumped in /suitescripts/ which is fine if there's only like 10 script files, but it gets silly fast I think generally people use a folder structure based on solutions I have seen them organized by script type, which... i personally don't think it brings much to the table... we use naming conventions that have the script type in the file name so there's never any need for them to be in their own type folders. git as a repo i think is pretty standard for deployments you can just modify the deploy.xml to only deploy the objects/scripts you need. there's certainly more that can be done with deployment pipelines and integrations to Jira (and its ilk) but I don't think they're essential
but there's no right/wrong answers here, just strong opinions and best practices... do what works, as things get more complicated you might realize what used to work no longer works then its time to make some changes.
t
An account customization project and using git are pretty standard. I don't think there'd be many cases where you can't get this to work. A folder structure based on each solution is good as well. Keeps it clean for whoever is working on those problems, but at the same time you really aren't looking at the folders that much. It's for whoever in the future needs to see it, they can see it based on the problem it solves
e
I've written a metric ton of words on how I think about these things: • My current git process • How I do tagging • How I handle hotfixes • Handling environmental drift • An older comparison of repo structures
👍 2
💯 2