changing format of unique opportunity id

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

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

Hey Michelle Plutto ,

Great question! And great answers from Francesca Shiekh !

As you hinted that you are thinking about an integration, I would use something else for it: the upsert api.

The upsert api (which I actually coded and built into the product a few years back, myself) works great with integrations by upserting (update or insert) data into Sugar with external identifiers. You can find more info about it here: https://support.sugarcrm.com/documentation/sugar_developer/sugar_developer_guide_13.2/integration/web_services/rest_api/endpoints/modulesync_keysync_key_field_value_put/

Especially if your end goal is an integration, I would consider that instead, as a starting point, as changing the approach down the road might be more challenging.

You could also leverage a combination of the two, if ongoing, you need a unique identifier in Sugar, when/if the source of new records is no longer the third-party system.

I would also consider creating your own "sync_key" type field (which needs to be coded) - for example call it "oracle_id". A working example of adding a new sync key field is here: https://github.com/esimonetti/sugar-new-sync-key-field

I've reached out personally, to see if you might be interested in consulting around this topic.

Hope it helps

Cheers

Hey Michelle Plutto ,

Great question! And great answers from Francesca Shiekh !

As you hinted that you are thinking about an integration, I would use something else for it: the upsert api.

The upsert api (which I actually coded and built into the product a few years back, myself) works great with integrations by upserting (update or insert) data into Sugar with external identifiers. You can find more info about it here: https://support.sugarcrm.com/documentation/sugar_developer/sugar_developer_guide_13.2/integration/web_services/rest_api/endpoints/modulesync_keysync_key_field_value_put/

Especially if your end goal is an integration, I would consider that instead, as a starting point, as changing the approach down the road might be more challenging.

You could also leverage a combination of the two, if ongoing, you need a unique identifier in Sugar, when/if the source of new records is no longer the third-party system.

I would also consider creating your own "sync_key" type field (which needs to be coded) - for example call it "oracle_id". A working example of adding a new sync key field is here: https://github.com/esimonetti/sugar-new-sync-key-field

I've reached out personally, to see if you might be interested in consulting around this topic.

Hope it helps

Cheers