This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Attributes of UNSAccountB not getting updated during an update

Hello,

We're running v7.1.2 at the moment and will be updating to v7.1.4 soon.

We've got Office 365 connected via PoshNet40/powershell connector and we're running into an issue where attributes like phone numbers for a user isn't getting updated in Office 365 when the user record is updated. New user record creation is fine. We can see the custom process getting fired and processed, however there doesn't appear to be any call out to Office 365.

We're using the UNSAccountB object as the account object type, with the default attributes set. The default attributes set does not include attributes such as phonenumber, mobilenumber, etc. We're just wondering if this is the cause of the updates not getting through to Office 365, as there is nothing to compare against for an update?

We've raised a ticket previously with support and they are equally perplexed, as there is no synchronisation log generated for an office 365 account update. Due to it being a custom integration, there is a limit to the amount of assistance they can provide.

If it's due to the UNSAccountB table not having the other attributes, is it as simple as extending the table with columns matching the missing attributes?

Thank you.

Parents
  • I am a little bit confused. So you are saying:

    • You do have have custom process chain, that should trigger the AdHoc - Provisioning when an UNSAccountB object is updated but this is not working.
    • You do have the process working for inserting an UNSAccountB object?
    • The properties you are trying to update in Office365 are stored where in OneIM?
Reply
  • I am a little bit confused. So you are saying:

    • You do have have custom process chain, that should trigger the AdHoc - Provisioning when an UNSAccountB object is updated but this is not working.
    • You do have the process working for inserting an UNSAccountB object?
    • The properties you are trying to update in Office365 are stored where in OneIM?
Children
  • Hi Markus,

    • You do have have custom process chain, that should trigger the AdHoc - Provisioning when an UNSAccountB object is updated but this is not working.
      Seems to be the case. I can see the custom process appearing in the queue monitor though when an update is triggered.

    • You do have the process working for inserting an UNSAccountB object?
      Yes inserting a new O365 record successfully carries the attribute values over.

    • The properties you are trying to update in Office365 are stored where in OneIM?
      They're stored in the person object.

  • When you look at the generated process in the queue. Does it contain the process step that executes the AdHoc projection to the target system? And if so, does it contain a value for the parameter ForceSyncOf?

  • Sorry Markus, it appears I was wrong about seeing the update process appearing. The one I thought was appearing turned out to be for AD, not Office 365. So we're not seeing an update process being triggered for Office 365.

  • Yepp thought so. Thing is, that the update event will not be triggered at UNSAccountB if no data is changed in UNSAccountB. The data you are changing lives in the person table.

    • Option A: Extend UNSAccountB with the necessary columns and implement the necessary templates to let the data flow from the person to UNSAccountB
    • Option B: Take a look at the Thumbnail update implementation for ADSAccount. The thumbnail is stored in the person only for this use-case as well. But this needs to have an update process on the person table that then generates the UPDATE (or any other) event on the UNSAccountB table and setting at least the value ForceSyncOf via the parameter collection. The parameter ForceSyncOf would then need to contain the column that triggers the update in a comma-separated list (as far as I know). Person.DefaultEmailAdress,Person.Phone,...
  • Thanks Markus. Option B looks good so we'll give that a go first. Many thanks for your quick assistance on this issue.

  • Hi Markus,

    Was the Thumbnail update to ADSAccount introduced in v8.x? I can't seem to find this attribute on v7.1.4.

  • The thing is that the thumbnail is not stored in the ADSAccount object but when the JPEGPhoto at the assigned Person changes, this change will be transferred to the AD User in AD using the ADSAccount AdHoc sync. There is a mapping definition for this use-case in each AD sync project since 7.0.

  • Thank you Markus. I have now located the configuration in the Designer and Sync editor.