How to refresh property values in database

Spirillen 2023-09-06 11:34:29 UTC #1

When a client no longer is applicable to an analysis, the data will dissappear from the computer summary and the analysis results, but it seems to be kept in the database and appear, when I get the results using RESTAPI or Presentation Debugger.
How can I refresh database values without having to remove and add analysis again ?

Thanks in advance

ageorgiev 2023-09-06 11:39:00 UTC #2

You can’t refresh the properties if they are no longer relevant. You need to change the relevancy of the analysis/properties, so they continue to report data and that will update it in the DB. Otherwise, Audit Cleaner in BES Admin tool is how it should get cleaned up, so depending how it is scheduled it should eventually cleanup not relevant data…

Spirillen 2023-09-06 11:53:38 UTC #3

But that means, that I have to evaluate every property out there on all clients and give a “dummy” value to those not applicable in order to create valid reports. Can you tell me, which part of Audit Cleaner removes data no longer valid, is it “Remove deleted custom authored content” ?

ageorgiev 2023-09-06 12:02:49 UTC #4

Well, you can enable the analysis with added relevance to a single computer or computer group, so it doesn’t automatically target everything; respectively increase the frequency of the reevaluations to let’s say 30 days (depends how old your data is though - if it is 2 weeks old and you set frequency of 30 days, even if you enable it won’t update it right away) BUT you are absolutely right, it’s not ideal…

It’s been a long time since I looked up the options of the Audit Trail (set it once years ago and never needed to touch it again) but if not mistaken should be "Remove data older than days: " value - if you have it set to 30, any data that is older than 30 days will get purged and since as you pointed this data is not getting updated will be “in scope”. Be careful though - similarly to the analysis approach, it’s setting that controls “everything”, so if you need to keep data for compliance purposes for certain period but need to delete faster for this just one property, it may not be good to drop the value as it will delete all data that is older than the threshold…

Aram 2023-09-06 15:58:18 UTC #5

I’d have to take a closer look, but I wouldn’t necessarily expect that such data would be returned via Session Relevance. That said, depending on your session relevance query, even if such data is returned, you could add a filter on devices that are applicable to the analysis as a potential workaround…

Spirillen 2023-09-07 06:45:42 UTC #6

In most cases we have solved this by adding a timestamp to the property, which we can use when retrieving the data, but in this last case, this is not a possibility, because this is a property, our license management people, uses in Inventory, so it is imported into Inventory as a computer property, which gives me no possibility to change the relevance.

ageorgiev 2023-09-07 07:54:43 UTC #7

Yes, Inventory as added downstream ramification does complicate things. Maybe worth opening a support case for the Inventory team to see what they have to say about it. Maybe it is something they should be looking at when they run their imports (“how viable is the data they import”) and clean-up if it’s old, irrespective of what the clean-up schedule on Platform side is.