Huge Impact: Vlocity Export Discrepancies with V2.4.5

[abdulhaseebsyed]

@Codeneos, Hope you're doing well.

I'd like to bring to your attention a few observations that are causing discrepancies during deployments.

I've attached some snapshots highlighting the issue. Up to version V2.4.3, the export behavior of the JSON files remained consistent. However, starting with V2.4.5, there appears to be a change in the export structure, which is impacting sequencing and leading to deployment issues.

Left: V2.4.3 (older versions)
Right: V2.4.5

There may be additional instances that have been affected in a similar manner, which leads me to believe this could be an issue introduced in V2.4.5.

Could you please investigate and help rectify this behavior? Your assistance would be greatly appreciated.

Thanks in advance.

DataRaptor DataPack

DataRaptor Mappings

Omniscript DataPack

IntegrationProcedure Elements (It's trying to add versions in VlocityMatchingRecordSourceKey)

[Codeneos]

@abdulhaseebsyed First of all thank you for brining this up.

I've been working on refactoring parts of the code to make them compatible with Omnistudio and reworking the export logic which does indeed impact JSON generation.

The re-ordering of element is very much an undesired side effect as well as the null and "" string behavior, my current regression tests do not account for this which is also the reason these defects crept into the code.

I'll spend soem time today to review your findings and see how to address them to avoid the big diffs in the exported JOSN output.

[Codeneos]

@abdulhaseebsyed I think I've nailed the issue.

Pre-release version 2.4.6 should fix the behavior and align the exports back to the old format also replicating the sort order of the elements.

If you do have a chance please test version 2.4.6 and let me know if that fixes the issues?

[abdulhaseebsyed]

@Codeneos, I've downloaded and installed the 2.4.6 VSIX. I'll run a few tests today and confirm the results.

There were also some issues with the Vlocity Cards JSON content, where the Vlocity namespace was not included in the extracted files. I'm hoping that has been addressed and fixed in this version as well.

[abdulhaseebsyed]

@Codeneos, Thank you so much for the quick turnaround! I’ve tested all the impacted scenarios, and everything is working as expected now. The faster export process is greatly appreciated as well. Hope we’re all set for a smooth and stable V2.4.6 release!

[abdulhaseebsyed]

@Codeneos, It appears there are still a few issues with V2.4.6. I just encountered the below error while testing. Few elements aren't exporting correctly in the JSON Structure.

Left: V2.4.3 (older versions)
Right: V2.4.6

I really like the V2.4.0, I do not encounter any issues of these sort in it.

[Codeneos]

@abdulhaseebsyed I should have actually versioned 2.4.2+ as 2.5 or 3.0 as the default exporter was changed from running in APEX to run directly from vscode using native SF APIs. This actually means the export should be faster, a lot faster if you export a lot of datapacks at once.

I've primarily tested the new function myself on a (big) product catalog but less on IPs and OS. As I have been using for a longer time already I hadn't spotted these differences especially as the deployments didn't give me any errors or failures.

And thanks again for providing me with the screenshots of the diff you see in your datapacks. My goal is exact format parity, I'll fix the remaining gaps I'll do another pre-release build.

PS: the line break change on empty arrays and objects from line 39-40 and 49-50 I will probably not be able to prevent.

[abdulhaseebsyed]

Sure @Codeneos, I look forward to test new pre-release build and confirm you :)