Need help on adding fields
I was tossed into the deepend of the Boomi pool and am learning to swim, so bare with me.
We currently sync FFs from one CRM to Salesforce using Boomi. I have a get that pulls a bunch of fields from the Opportunity object and are currently mapped in some processes. (you can probably see where this is going)
Some changes to our Oppty object now have me needing to add/remove synced fields. I've been told there is a way to do this WITHOUT breaking current mappings? If this is possible, can someone please explain the process so that I don't break my integration with a new import on my get?
Posted Jan 28, 2020, 7:48 PM UTC
16
I haven’t done much with SF but can you manually add a new field to your SF profile in Boomi? Your new field would be included in the payload automatically so you just need a spot in the profile.
If that doesn’t work then you would likely have to reimport the object from SF. This would kill your mapping but you can likely use Boomi Suggest to at least get some of the mapping done
That's what I'm really not sure about. My initial thought was to just re-import with the new fields added to the current selection and maybe that would just add the new fields?
There needs to be an easier way to do this since data changes constantly! UGH!
I totally agree! And yes re-importing will certainly grab the new fields for you. Just need to take some time to go back through your mapping
I'm thinking:
My biggest fear is the mapping. I mean, I could take screenshots and stuff like that, but if it breaks, then there is going to be some downtime and I'm not sure how much I would be allowed, lol.
Ideally, I could just reimport, adding the new fields to my selection and it would add them into the mapping areas without disconnecting any current mapped fields. This is my hope, but the fear of God was placed in me during my 2 week Training/Knowledge Dump back in August.
This is the first time this situation has come up in 5 months and now I am terrified!
Do you have a testing or staging environment? Because you could always try in staging and see what happens
Additionally you can always try and if it blows up just don’t publish to production and revert to your last deploy