Looking for a bit of advice on an issue my company is wrapping our brains around. We are redoing parts of our CRM and not able to figure out the best way to handle our activity entities. Custom activity entities vs custom fields on the out of the box entities
Currently we are using custom fields on the out of the box entities to meet specific department needs. Things like travel info (time/distance) for on site appointments, subject trees to set a category type for the record based on department and specific activity, look ups to custom entities, fields to assist with Outlook sync filtering, etc. This has "worked" so far but has had some limitations when using views, reporting and also making sure that the custom fields get filled out (creating in Outlook vs web).
Now we are looking at leaving the out of the box entities alone and creating custom entities to meet departmental needs.
Our main concern right now is getting these to sync into Outlook. For example, we created an On Site Appointment entity thinking this would flow into Outlook either as a task (doable but not ideal) or an appointment (best case) but it does not show up.
We can see the activity in Dynamics 365 Activity drop down in the Dynamics 365 tab. We can create the activity this way but it will not show up in Outlook. It shows up fine when looking via web.
We are using the Outlook client and not the App at this time.
