Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2022 Release Wave 1 PlanDynamics 365 release plan for the 2022 release wave 1 describes all new features releasing from April 2022 through September 2022.
2022 release wave 1 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
Firstly it is worth considering simple solutions if this isn't something that happens all the time and you don't want to any custom coding:
1. Export data from advanced find (new_processed contains U and new_date_issued contains data) - then export to Excel and mark for re-import. This will allow you to ad the start and end date and re-import
2. Create a workflow to update the start/end date to specific date and run the workflow in batches of 250 (set in user settings) on the results from advanced find. This would obviously mean that the workflow would have to change for different start/end dates.
For more detail - see iancrm.wordpress.com/.../microsoft-dynamics-crm-and-bulk-editing-records
You could use a third party product like www.c360.com/.../record-editor-online-360
If you need something more turn-key you could create a dialog that prompts for the two dates and then calls a custom workflow activity passing the two dates which in turn updates the dates by querying and updating using the Organization Service - msdn.microsoft.com/.../gg328515.aspx
Hope this helps,
Great info! Thanks for the guidance. I will focus on option # 2 and # 3 as that seems to be more in line with what I need.
Option # 1 is out - End users cannot be bothered with exporting and importing from excel every time they need to run this procedure. That method is unworkable as users will select a "start date" and "stop date" daily, and need all records with "issue_dates" that occur between those selected "start date" and "stop date" get their "processD" field automatically updated with a value "P" for processed. Then several reports need to open and those reports must be passed the same "start date" and "stop date" along with some other parameters.
Option # 3 is out as its a "3rd party product"
Option # 2 may work but I ran into trouble.... on the workflow, when I try and save it without actually selecting the start date and stop date, I get an error saying I must select a value for the dates... this value will always be different depending on what the end users are processing. How do I tell the workflow to return records that sit between a date range, where the date range is always specified by the end user and is always different?
Business Applications communities