You need to sign in to do that
Don't have an account?
Fix problems in an ORG or Create a new one?
Hi!
We´ve a big problem in our company.
When our team started to work with Salesforce here, there were a lot of customizations that has been done previously.
With this thousands of customizations, thousands of problems has been created as well.Some examples of problems:
- More than 200 sharing rules.
- More than 300 custom fields in account(we believe that 150 is rubish)
- Workflows that doesn´t works.
- Triggers and classes confused
- Lots of custom objects(unecessary)
Now, we´ve to develop new projects(customizations and integrations with legacy systems).What´s the best pratices to this case: Fix all problems in this ORG or Start using a new one and migrate the customizations from the old one?
Thanks so much!
Hugo
This is feature is not available default, but if you log a case to salesforce and request them they can enable the audit fields where you can enter the created date while inserting the record.
Thanks
Ankit Arora
Blog | Facebook | Blog Page
All Answers
You can go both ways either.
But salesforce provides user friendly customizations so it is very easy to create them on new org, in your case you just need to replicate. And every implementation from start is always good.
Also as explained that you have done customization in very large amount, there may be some places where problem can persists. Developing everything from scratch takes time, but it is the investment.
Thanks
Ankit Arora
Blog | Facebook | Blog Page
Thanks for answer Ankit.
But to transfer our data. Salesforce allow maintain in my new ORG the "Creation date"(same date from old org)?
This is feature is not available default, but if you log a case to salesforce and request them they can enable the audit fields where you can enter the created date while inserting the record.
Thanks
Ankit Arora
Blog | Facebook | Blog Page