Assets: How to separate or exclude Objects which are archived using the Archive function in Assets

Questions & Answers
, ,
1

Hey, new noob eazyBI user here. I was trying to create a simple report on eaziBI side to show me counts per Object Type for an Object Schema, and I stumbled on a count mismatch between what I saw in Assets for that Schema and what was shown in the eazyBI report. There were more objects on the BI side.
Found the culprit to be the fact that there were Objects in that Schema which had been archived using the Archive function.

So, my question is: Is there a way to filter or separate the rest of the Objects from Objects which have been archived on Assets side (but show up in eazyBI)? I couldn’t find a flag or switch or property to tell those apart. :frowning:

Using eazyBI version 8.2.0:node1 and Jira v10.3.12 in Data Center

2

Hi @andreas.sisas,

Welcome to the eazyBI community, and thanks for posting your question. It’s a good one!

Currently, archived Assets objects are imported as ordinary objects, and there is no dedicated flag or property to distinguish them from active objects.

However, there is a workaround: you can add an AQL filter in the Assets source application import options (under the “Additional options” tab).

Setting any AQL filter, such as:

Created IS NOT EMPTY

will cause archived objects to be excluded from the import automatically.

We do have a feature request logged to properly support archived Assets objects in eazyBI. We’ll update this thread if there’s progress on that front!

See Assets documentation

Best,
Marita from support@eazybi.com

3

Hey, @Marita_Burgio,

Thank you for your reply! I will test the proposed solution as soon as possible. Can you tell me the reason why this workaround would work? Just trying to understand the logic behind it.

Thank you!

Br,
Andreas

P.S. I will explicitly inform here, whether this proposed solution worked for me, once tested.

4

Hi @andreas.sisas,

The reason this works comes down to a handy side effect of how AQL handles archived objects: it simply does not return them in its query results.

So when eazyBI uses an AQL filter to import data, it relies on AQL to fetch the objects, and since archived ones are invisible to AQL, they never make it into the import.

Without any AQL filter, eazyBI imports all objects unconditionally, bypassing this behavior, which is why archived objects were showing up in your report.

Looking forward to hearing whether it works for you!

Best,
Marita from support@eazybi.com