-
Notifications
You must be signed in to change notification settings - Fork 1
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
Comments
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?
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
Thank you for using the PCF control! Kind regards, |
Hi Cathal,
Thank you for your response. When I open one of the blank rows, this is
what I see.
[image: image.png]
And here is a comparison of the old interface to the Unified Interface.
[image: image.png]
[image: image.png]
Thank you for the help!
Tyler
…On Fri, Nov 20, 2020 at 3:05 PM Cathal Noonan ***@***.***> wrote:
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
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA53T7PAUIYBMC7GM3JIAZLSQ3YZ7ANCNFSM4T5GUMYQ>
.
--
Tyler Daher
Undergraduate, Information Systems
San Diego State University
|
Hi tylerdaher, this is fixed in the latest release - v1.0.3.0 |
We got this implemented, and things look great!
![Snag_11a5c7c](https://user-images.githubusercontent.com/3914237/99845585-bbd6c480-2b29-11eb-81e9-152506fd7ec4.png)
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
The text was updated successfully, but these errors were encountered: