Hi Julius

Thanks for your comments, and you are correct in assessing this is for a specific use case (I'm migrating data between 2 structures and want to make sure the exported JSON is EXACTLY the same).

For the first point, I really only care that all values in the source are also in the target.   If I wanted to be thorough, I woudl run the compare in both directions, but since I'm expecting that the target will contain additional properties, I only need a 1 way compare)

For the second point, I actually define the ordering of exporting of arrays explicitly, so I would expect a like for like compare.   For other cases, additional logic would need to be added, as you pointed out

For the last point,  this should return a mismatch, which is good enough for my use case, but again, might not be ideal for other use cases

That would be an easy adjustment to make.  In my use case I'm also interested in knowing which fields are mismatching, and there may be multiple mismatches (hopefully not) per export 

HI Denny

Trakcare publishes it's CSPs as Deployed, so a standard install will not contain a user friendly way to view them



If I'm writing something that will  maybe run 2 or 3 times, and is less than 10 lines of code, I might use a .mac.  For anything more than that, I would use a class, as the time saved in setup is pretty negligible compared to the rest of the work done

Hi Jay

This has happened a few times, and I've readded them a few times.  I'll see if I still have the images handy and get them reattached again

Could you try making the call with a REST client like RESTLet for Chrome, and seeing if the request comes through on that method?

Try reading the Request data with this

Set updateJSON = %request.Content.Read()

Edited because I missed that you already tried this?

Hi David

Are you specifying the HTTP verb in the $.ajax call?