[CoE Starter Kit - BUG] DLP Impact Analysis export to CSV disabled
Opened this issue · 5 comments
Does this bug already exist in our backlog?
- I have checked and confirm this is a new bug.
Describe the issue
Hi,
DLP Impact Analysis "Export to CSV" button is greyed out. Have I missed something lately that makes disables this button?
I just tried to cover another environment with an existing DLP and the button is disabled. Is this expected behavior or is something wrong?
Expected Behavior
No response
What solution are you experiencing the issue with?
Core
What solution version are you using?
4.43
What app or flow are you having the issue with?
DLP Impact Analysis
What method are you using to get inventory and telemetry?
Cloud flows
Steps To Reproduce
No response
Anything else?
No response
I don't repro this. There is a ItemDisabled clause for this which looks as follows, but it appears that there are records in the table so it should be treated as true.
ItemEnabled: If(dlEnvironments.TotalRecords>0,true,false),
Can you please tell me
- Which version of Creator kit you have installed
- The type and region of your envt.
- Creator Kit Version: 1.0.20240529.1
- Region: Europe, Environment Type: Production
I'm not sure. I just dont repro.
Can you confirm the following:
- does this repro for all your DLPs? Or just some?
- what changes did you make to the DLP before getting to this page?
And also please share a screenshot like this so we can see what solutions you have installed in this environment? Be sure to show all records (all rows) and expand the indicated columns so that we can see full names
Weird stuff!
I have a rather restrictive DLP already setup for a dev environment (It blocks most stuff). In Data Policy Impact Analysis, editing that rule and adding the default environment to the rule to assess the impact. In the impact stage I see lots of impacted flows and apps but the export button is disabled.
Tried doing other changes to other DLPs (I can see apps/flows affected in Impact Analysis) but button is always disabled.
UPDATE: Think I found the bug! When adding additional environments to the DLP, I searched for the default environment, selected it and pressed "add to policy". If I do not search for the environment (and just scroll down the list to select it in the same way), it seems to work.
Thank you for the update. Will put on the list for the app owner to investigate.