Object Definition/ Transformation Inheritance Video Demo [5 Min]

Learn how to use Cloud Elements to set up default data transformations for your users. When enabling your customers to map their own data, it helps to provide them with default mappings to get started. Using this new feature, if your customer has a custom field they wish to map, they will have the ability to inherit the default mapping and extend it at the instance level without having to redo the work you put it to set up the default mappings.

In this demo, Brian Rothhaar, Cloud Elements Senior Engineer, will walk you through how to set up a transformation inheritance.

Video Transcription: 

  1. I'm going to go ahead and create an object definition at the org level, with a single field “theID”. It's labeled with ORG just to show where it came from when we do the inheritance.

  2. I’m also going to create a transformation at the org level, but I’m not going to add any fields to it though. I’ll add a “passThrough” configuration, to show that the configuration is also inherited.

  3. There is the org level transformation. There are no object definitions at the account level, just the one we have at the org level “myInheritenceObject”.

  4. Create an object definition at the account level, also called “myInheritenceObject”, and I’m just going to create a single field on this one as well, called “theName_ACCOUNT”.

  5. Now I have only the org level transformation here at the account level. So I’m going to create this transformation at the account level. I'll add the inherit configuration to this, meaning that when the transformation is used it will inherit any configurations from the parent.

  6. You will also see that I am mapping two fields in this transformation at the account level. The first one is from the org level and the second one is from the account level. If i didn’t have this inherit configuration it would fail. In this case “theID_ORG” didn’t match the object, but since I’m now inheriting, I’ll get that from the org level object definition and this one from the object level definition. 

  7. I will create that transformation now, you will see it created when I go and retrieve it. It actually will GET the inherited integration from the org level, and both of the fields mapped as shown before.

  8. Now I’m going to call that transformation when I go out to Salesforce. So there you go, it worked: We got “theID” from the org level, “theName” from the account level and the inherited “passThrough”, which means we are filtering out all the other fields that weren’t explicitly listed in the transformation.

  9. Now I’ll show, one more level at the instance level, again the only object definition listed when I retrieve object definitions for the instances are the ones at the account level. So I’m going to create one, again similar to the account level, i’m just adding a single field. It’s called “theMod_INSTANCE” to show that it’s at the instance level. And I’m going to create a transformation at the instance level as well.

  10. In this one, again I’m inheriting from the parent, so it will inherit both the account level and the organization level, and I’m overwriting that passthrough configuration at  the org level and I’m adding one field mapping for the “theMod_INSTANCE” field.

  11. When I go out and retrieve it, it will inherit the two field mappings from the account level, which were these two, including the one field we added at the instance level. Again, we have the inherit config set and we’ve overridden the pass through config that we set up at the org level.

  12. Now when I retrieve my inheritance object from Salesforce, you will see that all three fields are now mapped. We have “theID” from the org level, “theName” from the account level and the “theMod” from the instance level. And also since we overrode the pass through configuration, we are getting all of the fields.

Previous Video
Introduction to Element Builder Video Demo [4 Min]
Introduction to Element Builder Video Demo [4 Min]

Learn how to edit existing API Integration available in the Cloud Elements Catalog using our integration to...

No More Videos