Breaking news from around the world
Get the Bing + MSN extension
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2019 release wave 2 Discover the latest updates and new features to Dynamics 365 planned through March 2020
Release overview guides and videos Release Plan | View virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
I have a Real Time Workflow running On Create of a Note from the LMS Document record that needs to create a custom LMS Document Attachment record (this will hold the Version information from the LMS Document Version child record).
It first checks that the Regarding LMS Document (which is the Parent record to the LMS Document Attachment') IS Document, then should create the LMS Document Attachment. Here are the relationships.
LMS Document : LMS Document Attachment 1:N
LMS Document Attachment : LMS Document Version 1:N
LMS Document : Note 1:N
LMS Document Attachment : Note
The Workflow is currently not getting past the first step - and I am getting the above error. It goes and performs some other steps as seen below. Here are some screenshots.
Can anyone assist in what is wrong here? Thanks so much in advance for your thoughts / suggestions.
If I understood correctly, in your "IF" clause you are saying that the field "Regarding" of your Note is an entity LMS Document. But then, on your third step (the update step) you are trying to update the entity LMS Document Version on the regarding field.
That is, on your IF you are saying and confirming that the regarding field points to LMS Document entity but in the third step you say that the entity on that field is LMS Document Version. Since what you have is a LMS Document , it will fail saying that there is no LMS Document Version entity to update.
I'm not sure if my reasoning is correct, but it was what I concluded with your explanation and screenshots.
Thanks for responding, Joana - I really appreciate it. So, the first step is below. It needs to check that the regarding is an LMS Document, and if so, Create a Document Attachment.
The second step then creates the Document Version, which is related to the Document Attachment that was just created. Why I am confused is why it is failing on Step 1. All the relationships should be there. Which record cannot be found to be updated?
It's not failing on step 1. In this image, you see that is failing on the update (as the error message itself says):
Your IF is correct and it passes correctly by that IF. The record that cannot be found to be updated is the LMS Document Version (I signalized it on the image above). Your regarding field is a LMS Document record, not a LMS Document Version
Thanks again! OK...so if steps 1 and two (Create LMS Document Attachment and Create LMS Document Version are good, then maybe I do not need step 3? But I need to update the LMS Document Version to increment by 1, and then put that value on the LMS Document Attachment field. Suggestions?
It's hard to explain on written lol.
You can update the LMS Document Version and increment by 1. The problem is you are accessing the field "Regarding" and saying that the entity in there is a LMS Document Version when it's not. On step 2 you are creating a LMS Document Version record but you are not associating it to the field "Regarding" on Notes entity. You've just created the record. To update, on the next step (3) you must update the record you've just created and not the "Regarding" field.
Got it...had to update the 'Create' record - duhhh. Thanks so much! Huge help. You made my morning.
Nice! Glad to help :) Cheers!
Cheers to you! Sorry - one other question...the Workflow is creating the LMS Document Attachment, and the LMS Document Version, but is not incrementing the Version No. (Decimal Field) on the Update step. Any idea why this would be?
Can you send some screenshots again? Thanks!
Sure thing. Here is the WF as it stands.
The 2 Create steps are working, but the 2 Update steps are not. I have posted the 4 in order.
I also would like to set the Status of LMS Document Version to Inactive in another step, and also update 'Current Version' on the LMS Attachments
Create LMS Document Attachment:
Create LMS Document Version:
Update (Create) LMS Document Version:
Update (Create) LMS Document Attachment
Basically, on the LMS Document Entity, I want to show a Sub Grid for the related Attachments, with versions so the User can see all, and which ones are latest versions, etc.
Thanks again for your help on this.
On workflows you have an option of increment a value, like this:
Is this what you are doing?
Correct - here is the step, and the screenshot. It is not incrementing the 'LMS Document Version No.' field on the LMS Document Version entity in the Update step...
I think it is. You are incrementing a value of a record that has been created. So, by default, the decimal value of the field will be 0 (unless when you are creating LMS Document Version record you are giving a value for LMS Document Version No. different than 0). If not, the default value will be 0, so the increment of that will be 1.
OK, makes sense. So what would you reccomend? Setting the default value of the Version No. in one step and then incrementing? Maybe using an Autonumber on that entity/field instead (I use a Counter on other entities to set Name). Open to suggestions...:)
Well, that depends on what triggers the increment process and how it's done. The increment is always "previous value + 1" or is something like "value form other entity/field + 1". For the first case, an auto number seems sufficient. For the second scenario, I would have to know more about the business logic to advice you correctly :)
Business Applications communities