Assigned User field population

[tblock10]

We are currently populating Assigned user from a custom hardware asset business importer. We are contemplating removing the Assigned to from that import to allow Flexera to populate all the user fields. Will the currently populated Assigned users be overwritten if we synchronize Assigned user with Calculated user?

[tjohnson1 · Accepted solution]

When the setting is first enabled the Assigned User will be set to the Calculated User as part of the subsequent import/reconcile. Then any changes to the Calculated User will also update the Assigned User.

https://docs.flexera.com/fnms/EN/WebHelp/index.html#topics/System_Settings-Inventory_Tab.html 

[Techbpn8771]

Should these fields be kept separate in terms of updates, can the 'Calculated User' field be updated via business adapter manually?  There is an item in the computer object called 'Calculated User ID' which seems to imply such  as currently we have an adapter using 'Assigned User ID' which works properly.  

Additionally, if the CU field can be altered via adapter, will the field automatically be updated by SCCM integration?  We are currently seeing an issue in our solution where a device is not receiving a calculated user via that integration due to the mapping field being blank on SCCM side.  Should we manipulate CU and for whatever reason SCCM mapping field becomes populated, will the manually set CU be replaced with the mapped field value?  Or is there a flag that flips causing any automatic mapping to not change the field if it is altered via import.

[ChrisG]

The Calculated User field on a computer (inventory device) can be set using a business adapter, but in general you should arrange things so that this is only done for computer records which are not imported from some inventory source (such as SCCM). If you try to set this field on a computer whose fields are also being populated using data imported from an inventory source then you will likely end up fighting against the inventory data that is being imported, with values flip-flopping between the value set by your business adapter and the value set based on imported inventory data.