Details about this thread
  • State Suggested Answer
  • Replies 7 replies
  • Answers 1 answer
  • Subscribers 321 subscribers
  • Views 15300 views
  • Users 0 members are here

changing format of unique opportunity id

Nikhil Kunnathully

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.

Parents
  • 0

    Hey  ,

    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)

    www.naonis.tech


    Feel free to reach out for consulting regarding:

    • API Integration and Automation Services
    • Sugar Architecture
    • Sugar Performance Optimisation
    • Sugar Consulting, Best Practices and Technical Training
    • AWS and Sugar Technical Help
    • CTO-as-a-service
    • Solutions-as-a-service
    • and more!

    All active SugarCRM certifications

    Actively working remotely with customers based in APAC and in the United States

  • 0 in reply to Enrico Simonetti

    would this work with importing from Oracle into Sugar meaning would this be an identifier we could count on?

  • 0 in reply to Michelle Plutto

    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

Reply
  • 0 in reply to Michelle Plutto

    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

Children