hey guys is it best practise to import all of the objects to the Objects folder with SDF? (sandbox)

I try to import as many objects as possible that are relevant to scripts as the first priority. But there will be times where certain objects can make things more complicated. Objects that reference 3rd party Bundles or SuiteApps for example are a pain because it will make your SDF project dependent on those outside apps.

we were thinking of making an identifier for all object id’s, doing it like this: custscript_[identifier]_scriptname but we are already halfway in some projects... (too much hassle) 😅 all new projects we are likely going to implement this.

yes, the identifier makes it easy to see and download all your customizations in one go. I did change a project in the middle but it was worth it in the end.

i’ll have to pick up the slack then 😅 thanks @tuli

The company I work for always include an identifier so we know definitively the objects we created. As an NS partner you often find bundles and scripts from 3rd parties and internal users in a customer's account so it's good to have that clear view. If it's a small project I tend to include all the objects for that specific project. On bigger projects where several devs are working on it, we tend to pull in the script objects specific to our own responsibility and then generate a secondary "general" webstorm project with everything else in, such as tabs / forms / workflows / custom records etc. In GIT we have an overarching project repository and then for each area we add in the specific webstorm project folders...but that's a whole different conversation.