Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Blank Rows #2

Closed
tylerdaher opened this issue Nov 20, 2020 · 3 comments
Closed

Blank Rows #2

tylerdaher opened this issue Nov 20, 2020 · 3 comments
Assignees

Comments

@tylerdaher
Copy link

We got this implemented, and things look great!
Snag_11a5c7c

One thing we see though is that we have a large amount of blank rows in the background processes. Is this because the workflows were set to be deleted after execution? Is there a way we can filter these out?
Thank you,
Tyler

@cathalnoonan cathalnoonan self-assigned this Nov 20, 2020
@cathalnoonan
Copy link
Owner

Hi Tyler,

It seems unusual that these rows do not have a value in the 'Name' column

This isn't something that came up while I tested the control -- you may have found a bug


Can you open one of these Blank rows and include a screenshot of what opens?

Double clicking on a row will open the "workflow run" in a pop-up window or new tab

(blur out any sensitive information as it is a public thread)

It's possible that these rows in the grid refer to something implemented internally in D365 as part of the opportunity entity..

Ideally we wouldn't see so many failures in the grid though! 😃


As an aside; if you still have access to the record in the classic interface, could you check and see if these blank rows also appear within the Background Processes section for this record?

If the D365 environment is using unified interface only, we can still get to the classic interface by replacing appid=<<guid>> with app=d365default inside the querystring

eg: https://my-org.crm.dynamics.com/main.aspx?app=d365default&pagetype=entityrecord&etn=opportunity&id=3fc9260b-5a4f-ea11-a818-000d3ab95de2


Thank you for using the PCF control!

Kind regards,
Cathal

@tylerdaher
Copy link
Author

tylerdaher commented Nov 25, 2020 via email

@cathalnoonan
Copy link
Owner

Hi tylerdaher, this is fixed in the latest release - v1.0.3.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants