Check out the latest features available in Dynamics 365 for Customer Engagement, including LinkedIn Connect, Voice of the Customer and Universal Resource Scheduling.
Dynamics 365 2019 release wave 2 plan Discover the latest updates to Dynamics 365.Release Plan | Weekly Deployment Notes
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 and Operations TechTalks | Customer Engagement TechTalks | Talent TechTalks
CRM doesn't seem to update the 'Modified On' date of a record (Opp, Lead, etc.) when either a Post or Note is added. I imagine I could create a workflow to do this but it doesn't seem like the relationship(s) between Posts, notes and Entities are set up the same way as other related Entities.
Any help would be appreciated.
Hello Joe Dubs,
You can create a work flow on Note, Activity and Post entity that run when create a record.
Please refer to : community.dynamics.com/.../create-a-workflow-in-crm-to-alert-a-record-s-owner-when-an-activity-note-is-added
Hope this helps,
Thank you Abed. I will take a look at the link you provided.
Hmm, this might be a silly question but can you update the 'Modified On' field via workflow? I don't see it as an available field in the 'update record' dialog.
Well, I worked around this by populating a 'placeholder' date field. Then the process execution itself updates the Modified On date.
Now, my second problem is that Posts do not have a relationship set up the same way as Notes, therefore there is no 'Regarding (Lead)' option in my Check Condition.
You can add Update step to update Regarding (Opp, Lead, etc.) in the same Workflow, and set its property to update any field on (Opp, Lead, etc.) this will change the 'Modified On' field :)
Yes, I got that part to work. My problem now is with setting up the Post(s) workflow. There is no defined relationship between Posts and/or Leads & Opportunities. (see image)
You need to select regarding field in Post (primary entity)
That only allows you to select a unique record. Even still, I am presented with another problem in that I cannot 'Update' any regarding records via the workflow either. (see image)
You are right Joe, the relationship isn't directly available in the workflow. Since the system doesn't allow it directly, try using a workflow to create a post so that you have control on the regarding entity record.
Since you are referring to Lead/Opportunity, I assume that you are using the system defined rules for post creation. You could try deactivating the rule that creates the post (the one that you are using) and create a workflow on Lead/Opp to Create a post and also update the record so that you have the ModifiedOn.
Refer this for post creation using workflow
Joe did you get any traction on this? Looking at the same issue, particularly with posts.
There is a scenario that you may want to consider - the deactivated or read only record.
You can still create notes or posts for a deactivated record or read-only one, which may not be your practice, but in such a case, your workflow will not be able to update the modified date on your parent record.
Have you considered using a joint table to achieve this? I would even use a custom activity type because it has the built-in regarding field, for example, so when you create a note for an Opp, you create or update this joint table. so for you to look at the last modify date, you will have to look at this joint table instead.
No, not really. Was able to configure workflow for Notes, but nothing for Posts.
This seems to be an issue within the Dynamics CRM plugin too. We are tracking emails against Cases from Outlook which adds an activity record to the Case in CRM. This doesn't change the modified date. I would expect the modified date to be changed whenever something is added to the Case entity.
Performing a change directly in CRM on the case itself does change the modify date (that’s when you manually click the floppy icon at the bottom right corner to save changes).
Nowadays I would rather use a rollup field to fetch the last activity date from child-activity-records than to start a workflow for each and every child record to update the modified field.
You will have to create a rollup field for each child type and then just use a calculated field over those to get your latest modified date.
Put those field in a nice section and you have a nice overview of what happened with the parent record.
Problem is that Post and Case\Lead\Account etc are not directly connected
I created Action that returns Case.
And Wf that calls that Action passing PostRegarding as a Target.After that in Wf i use CaseID returned by Action.
Business Applications communities