Handy tips while working with Salesforce Vlocity Dataraptors – User friendly Tech help
Problem- How to improve productivity while working with Dataraptors
n
1)Always start with creating new version of the dataraptor, it avoids overwriting the existing stable changes, or you can always fall back to previous versions in case your changes don’t work as expected.
n
2)In Extract Data raptor, to fasten the mapping process, its better to copy the expected Json from Omniscript Perview and paste in Output tab of dataraptor.
n
- n
- n
- n
- Let’s do it together
- Copy JSON from omniscript preview, for example we are planning to showcase account fields in omniscript, so we start with OS first and back engineer it.
Preview OS - Create dataraptor
- Output > Expected Json output > remove the extra JSON, just keep the one you require for the given OS fields
- Add new mapping > Output Json Path (it will show the required Json that is required in OS), map this to your account fields. This is helpful when working with large set of objects, rather than going back and forth in OS, you can get all the required object field names in dataratptor.
n
n
n
n
n
n
n
n
3)To improve performance of dataraptor, don’t try to fetch more objects in 1 DR, as more objects mean more SOQL queries to SFDC, thus degrades the performance, in case its required an alternate formula field can be used to map 2 objects in SFDC and in DR, we can have single objects to fetch the required fields.
n
n
4)Enable field-level security in Dataraptor
n
5)Using Null value, in filter criteria of dataraptor by using “$Vlocity.null”
n
Dataraptor Null
