Orchestration caching frustration - Cross Reference

 Perhaps this is just me and my dodgy use case.

I'm using jitterbit and JD Edwards orchestration to synchronise the address book between MSFT CEC and JD Edwards.  Nice and simple.  

I have a JB developer doing his thing and I said that I would donate my time to do the orchestration development - coz I'm a nice guy.

All started well and is not ending well.

A super simple start...  well...  There are no fields in the addressbook that are long enough to take the 40ish character CEC unique ID. I thought that an easy thing to use would be cross reference.  This is designed for this purpose... right?

So I start checking for my new AIS cross reference, if it does not exist - create it with the AN8 record

Easy hey?  Then I I do a similar check for edit and I delete both on a delete!  The perfect crime.

And finally delete

It's all fine until you string it all together.

Add:

Works fine.  Cross reference says it aborted, but it's configured to continue.  This is dodgy.  We can see that the AN8 has been created and now there is a value in the cross reference.

and AN8

I can now run all of my edits, all work well.  Address changes and cross reference picks up the add without an issue.

I run my delete:

I can see that the cross reference has been deleted and the AN8 is gone

See above that 06 is now missing.  BUT - if I try and create it again...  Everything craps out, because the value is cached in AIS

I think personally that is a bug.  If we are using highly dynamic reference data [which is reasonable], then I believe that the cache should stay current with the list.

You need to clear the JAS cache for this to work - crazy I feel.  

Anyway, this took me quite a while to find and makes me think I cannot use cross reference.