Solutions for Purging Specific Records in ControlUp Custom Index

A team member asked about purging specific records from a custom index using the API. Luke responded that it is not possible at this time and suggested raising a feature request. The team discussed different solutions and came up with a suggestion from a PS engineer to use a local script that creates and checks for a file before sending data to avoid duplication. The purpose of the data is for OneDrive migration planning.

Read the entire ‘Solutions for Purging Specific Records in ControlUp Custom Index’ thread below:

Hi all,

I am gathering some data from our user profiles by running a script @logon complete in the users context. The data is sent to a custom index.

As the device is the primary key in the index, using the ‘overwrite data’ checkbox is no option. (When a user logs on to another device the previous record of that user/device from the custom index is overwritten.)

Now my question is, can I purge specific records from my custom index by using the API (or workflows)?

@member of top of my head i don’t know let me ask internally see if this is possible

@member sorry to say but not possible at this time. you would need to raise a feature request

https://support.controlup.com/docs/submit-and-vote-on-feature-requests?highlight=user%20v

Thank you Luke for your swift response, going back to the drawing board 🙂

What is it you are trying to achive?

CU4D is gathering around 40 values after a user is logged on as preparation for our OneDrive migration (if folder redirection is applies, folder sizes etc).

This data is stored in a custom index. So every logon an entry is added to the custom index. Users are able to logon to multiple devices.

With a local PowerShell script I use that data, through the API, to generate an Excel document based on all our local AD users.

This document is needed to give an insight for our ‘desktop’ team to plan the migration.

I assumed that when a custom script is executed in the user context, the username was the primary key in the custom index. But that is not the case, it is the device. ‘Overwrite data’ enabled on the custom script will overwrite the data of that device. That was the primary idea to keep the data in the custom index in control.

For now, I think the way to go is to get the API call getting 10.000+ records for me.

In my local script I loop through all our AD users and check if they have logged CU data and for each unique combination found of user/device I will add the most recent record to my result list. At the end we know which user has logged on to which device and the specific settings for that device/profile.

suggestion from one of our PS engineers – you could write a file as part of the script, and also check for the same file before it runs. If file exists, script has previously run / don’t send data and exit, otherwise run rest of script and send data

Continue reading and comment on the thread ‘Solutions for Purging Specific Records in ControlUp Custom Index’.  Not a member? Join Here!