Hi Steven,
glad to hear this.
Best regards,
Andrea
Il 28/11/19 16:15, Steven van der Merwe ha scritto:
Hi Andrea
Thank you very much - You are spot on.
It was the fact that it was expecting an array but I was accidentally
passing back an array of arrays
It seems that it is all working
Hi Andrea
Thank you very much - You are spot on.
It was the fact that it was expecting an array but I was accidentally
passing back an array of arrays
It seems that it is all working now and propagating correctly.
Thank you all very much for your help, it is very much appreciated
Regards
Hi Steven,
the error that you are experiencing is quite generic. But usually means
that the key that you passed from Syncope is not matching the key of the
object that the connector framework retrieved with the query method. As
"not matching" I mean that the EqualsFilter [1] (or
Hi
I managed to work out why it was not propagating the __UID__ - It turns out
I had the config for the "mapping" the wrong way around.
I have now moved a bit further forward but I am stuck on the following
java.lang.IllegalStateException: Object {Uid=Attribute: {Name=__UID__,
Hi
I am still a little confused for the following reason. In my search method
there is no __UID__ anywhere am I missing something?
For context my executeQuery looks like this (my log function uses recursion
to print out all of the values)
@Override
public void executeQuery(
final
Perfect - thank you very much
I will try
Regards
Steve
On Mon, Nov 25, 2019 at 11:05 AM Francesco Chicchiriccò
wrote:
> On 25/11/19 09:47, Steven van der Merwe wrote:
>
> Hi Francesco
>
> Thank you very much for your reply - I think you have hit on the problem.
>
> Based on your response I
On 25/11/19 09:47, Steven van der Merwe wrote:
> Hi Francesco
>
> Thank you very much for your reply - I think you have hit on the problem.
>
> Based on your response I think it is definitely the read logic that is the
> problem since CREATE -> Creates, UPDATE -> Creates, DELETE -> NOT_ATTEMPTED.
Hi Francesco
Thank you very much for your reply - I think you have hit on the problem.
Based on your response I think it is definitely the read logic that is the
problem since CREATE -> Creates, UPDATE -> Creates, DELETE -> NOT_ATTEMPTED.
My problem is that I do not want to read from the
Hi Steve,
first of all, thanks for your words, they're highly appreciated.
Coming to your issue below, I believe the problem is either related to your
mapping configuration or Connector's READ implementation.
Having [1] as background, propagation to an External Resource works as follows:
CREATE
