You’re offline. This is a read only version of the page.
803
We have a database with text fields that our users can "highlight." All Contacts and Users in this database are the same as in Dynamics. When we highlight text fields, we are going to push this information to Dynamics, and create a new record that contains the "highlighted" text.
I was thinking we could use Task for this, but we already use the Task entity a lot, and it seems like it would clutter things up. At the very least, we'd need a check box on the Task form to differentiate between "highlighted text records" and normal task (so we can create different views). What I was thinking was creating a custom entity, and creating a record here each time a user highlights the text in our other DB. Then, when a record is created here, I thought we could create a Task to "review highlighted" text. That way we can save these records in their own entity, and also keep using the Task entity in a way we're accustomed to.
However, we want to keep things simple. How is it working with OOB entity APIs vs. custom entity APIs? Anyone have any thoughts on the overall structure, best practices, or things to keep in mind with respect to this project?
*This post is locked for comments
I have the same question (0)
the API is exactly the same in handling CRUD operations (Create, Read, Update, Delete) for OOB entities and custom entities
if you want to store highlight text then create an "highlight text" custom entity, better than re-purpose an OOB entity (especially when it is already used)
Share
Report
All responses (
Answers (
