You’re offline. This is a read only version of the page.
Hi Everyone,
I am estimating what will be required to migrate a business unit's usage of Dynamics CRM 2011 to Dynamics Customer Service online. They currently make use of Case/Incident entities more so than Tasks and Activities. A direct entity-to-entity migration from CRM 2011 to Dynamics Online will likely have them using Cases inappropriately.
In CRM 2011, Cases had a Form Assistant which allowed them to fill in the Subject and other form fields through a list of Dynamic Values. During my limited experience in the free trials of Dynamics Customer Service, it appears there is no auto-population or form-assistant style of behaviour for tasks and activities.
Assuming a migration to Tasks/Activities was proper (to-do items and customer interactions are the real world purpose) What options would there be to substitute the Form Assistant behaviour? I am seeking to avoid Solution-customization as much as possible. So far, adding a new field appears to be a simple addition -- although adding a hundred field option set entries is tedious.
*This post is locked for comments
I have the same question (0)
Share
Report
All responses (
Answers (
4
