+6Hey guys -
Quick question about naming policies. I was told by a colleague to avoid using spaces during package creation. Does this carry over into naming Policies as well?
I haven't encountered any issues with using spaces in the past, but we are in the process of rebuilding our entire database and I would like to look out for some best practices moving forward.
Thank you!
+16FWIW.... We use spaces in both packages and policies without issue. When creating custom triggers, I do try to avoid them there, and just come up with a simple trigger.
+16There were some issues a year or two back with spaces in package names and HTTP/HTTPS/JDS distribution points. I generally avoid it when creating packages as a matter of habit, but when I use a package direct from a vendor or from another source, I normally don't rename it.
+17There is an issue with package names and caching. As of my post here, "PI-004278-Cached Package filename removed from DB if Package Display Name and File Name differ" is a real thing and hasn't been addressed as of yet.
I would say as a rule of thumb, not to leave spaces in packages or scripts... but policies should be ok as we use spaces in our policy names. The only thing I need to do more digging on is the execution order on policies when they execute back-to-back-to-back...
+16We have used spaces in names for both since day dot without issue.
Interesting comment by @benducklow though, because we also keep the package and display name identical in 99% of case, just because I am picky about stuff like that and get upset when things don't match!
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.