Within ScalePad Lifecycle Manager, if a client name does not match precisely across your integrations, it is marked as a different client.

In this case, our system can see instances of one asset belonging to multiple clients from across your integrations.

To correct this, we recommend doing the following:

  1. Navigate to your Issues page.

  2. Click the Show Responsible Hardware Assets button on the lower right of the issue message to have Lifecycle Manager show you which hardware assets are causing the discrepancy.

  3. Click on the name of the first affected asset, to access the Asset View.

  4. There will be one or more crossed-out clients in the Client column. This will be the entry causing the issue.

  5. Click on the hyperlink from the Integration column of the issue entry to access your integration view.

  6. Remove the asset from the integration or update the client name.

  7. Repeat for each asset until you have solved all the inconsistent client names.

  8. Once this is done, navigate to your Dashboard and click Sync now to bring our platform up to speed with the changes.


Client Linking

Use our platform Client linking feature to connect the names in-app to resolve this issue.

Once you've used our Client linking feature to consolidate each affected client name, this issue should resolve successfully.

Alternatively, you could visit each of your integrations and rename each of the affected organizations.


Duplicate Assets

A duplicate assets issue can also cause inconsistent client names.

A duplicate occurs when an asset has multiple records syncing in from one of your integrations. This can cause inconsistent Client names when there are conflicting Client names for the same asset.

We recommend viewing the Duplicate assets article to track duplicate assets down and remove them from your integrations. After these duplicates are removed, the inconsistent client names will also disappear.

Once any changes have been made in your integrations, navigate to your Dashboard and click Sync now to bring our platform up to date.

Did this answer your question?