1. UNIFYBroker Forum
  2. PowerShell connector
  3. Questions
0
Answered

How is $components.InputEntities populated?

Carol Wapshere 9 years ago in PowerShell connector • updated by anonymous 9 years ago • 3

I have an IdB Powershell connector talking to Office 365. One of the IdB schema attributes is “Alumni” (Boolean flag). I populate this on import from O365, so it’s not something that is flowing from FIM. (There are reasons why it has to be like this to do with AADSync delay.)


Question is: if entity[‘Alumni’] has been changed on Import, will this cause the entity to be part of the $components.InputEntities when the Update script runs on export?


I know if the change comes from FIM via the Adapter it will be in that collection – just want to understand what happens if the change came from the Connector instead.

Answer

+1
Answer
Carol Wapshere 9 years ago

I'm going to get around it by setting a Boolean value to 'true' on connector import if certain conditions are met. FIM has a constant export flow which sets the flag back to 'false' - so this should ensure the object is included in $components.InputEntries to the Update script.

Searching answer
Adam van Vliet 9 years ago

Hi Carol,


$components.InputEntities will not contain leftovers from the previous operation. If you want it to contain the last set of imported changes, you'll need something in FIM to push the entity out again. Depending on your use case, you could then make use of the new $components.OriginalEntities set in v5.0 (see Export Changes).


Please let me know if this answers your question, or if you need clarification or a feature request.


Thanks.

+1
Answer
Carol Wapshere 9 years ago

I'm going to get around it by setting a Boolean value to 'true' on connector import if certain conditions are met. FIM has a constant export flow which sets the flag back to 'false' - so this should ensure the object is included in $components.InputEntries to the Update script.

Answered
Adam van Vliet 9 years ago

Customer support service by UserEcho