I am in the process of building a task management PowerApp ModelDriven App. There is already a default "Task" table available, but I am not sure if I should use it and extend it with relations or create a completely custom table.
The advantage of the default available ones would be that they are also integrated with Outlook tasks etc. However, I am afraid, since this table is also used by Dyn365, that I run into a, let's call it fields conflict - so in other apps are then suddenly mandatory fields available, which are not relevant there.
What is your opinion about this?