Is there a way to change the unique opportunity ID for all new opportunities moving forward? we wanted it to be numeric and short for our reporting.
Is there a way to change the unique opportunity ID for all new opportunities moving forward? we wanted it to be numeric and short for our reporting.
Hey Nikhil Kunnathully ,
While technically it is possible, I strongly advise against it.
The system is built to work with a 36 digits guids and changing that could create many unexpected behaviours. I've seen it done and nothing good comes of it.
If you need something for reporting, I would create a new field, and if it is suitable for you, create an auto increment field
--
Enrico Simonetti
Sugar veteran (from 2007)
Feel free to reach out for consulting regarding:
All active SugarCRM certifications
Actively working remotely with customers based in APAC and in the United States
would this work with importing from Oracle into Sugar meaning would this be an identifier we could count on?
Are you simply importing or syncing?
If you are just importing you could simply save the Oracle ID or Oracle Customer Number (in the case of Accounts) in a read-only field upon import.
If you are syncing then I suggest a mapping table, we have one with columns for OracleID, Sugar ID, SugarModule to map Accounts(Customers), Contacts and Addresses (we have a custom module for addresses in Sugar). You need to take a lot of care when merging records though... and it has been a bit of a nightmare since triggering a merge in our older version of Oracle is not an option.
FrancescaS
Are you simply importing or syncing?
If you are just importing you could simply save the Oracle ID or Oracle Customer Number (in the case of Accounts) in a read-only field upon import.
If you are syncing then I suggest a mapping table, we have one with columns for OracleID, Sugar ID, SugarModule to map Accounts(Customers), Contacts and Addresses (we have a custom module for addresses in Sugar). You need to take a lot of care when merging records though... and it has been a bit of a nightmare since triggering a merge in our older version of Oracle is not an option.
FrancescaS
currently importing but hoping to integrate soon. Guess best to just wait until we know how long before we are going to integrate
You may want to import something to match back to the original Oracle record just to have something to refer back to and match up existing records when you do integrate.
If you can, the OracleID would be ideal, if not, at least a Customer Number on Accounts....