Designing Data Structures for Journal Events and Attachments in Microsoft Power Platform Solution

Correct Answer: A

Dataverse provides the three types of tables (entities): Standard - this is a usual custom table type user can create.

These tables store data and navigation for model-driven apps.

Activity - this is a special custom table type for storing activity information like appointments, phone calls, emails, tasks, etc.

Virtual - this custom table type has columns that bring data from external sources, like Azure SQL Database or Azure Cosmos DB.To store activity information, like a journal, you need to use an activity table type (Number 1)

This type creates columns that help you store the journal data, such as start and end time, date.

Also, Dataverse provides columns to capture the activity purpose, like subject and description.

When you create a table, there is a check box for the Enable attachments option (Number 2)

If you check the box, the app will store multiple files or notes for each journal record.

Options B and F are incorrect because a virtual table brings data from an external source that is not applicable in this case.

Options C and E are incorrect because you need to use an activity table type instead of a standard custom table.

Option D is incorrect because if you add the Attachment column, you can attach only one file to the journal record instead of several.

For more information about the Dataverse table types, please visit the below URLs:

To design the new data structures for SeeTheWorld's travel journal functionality in the Power Platform solution, the following options can be considered:

Option A: One activity table with enabled attachments option This option involves creating a single table to store all the journal events with an enabled attachments option. With this option, each journal entry is stored as a record in the activity table, and customers can attach multiple files to each journal event. This option can be a good choice if there are not too many fields associated with each journal entry, and if the existing activity entities in Dataverse meet the needs of the journal events.

Option B: One virtual table with enabled attachments option This option involves creating a virtual table with enabled attachments option to store all the journal events. With this option, the virtual table acts as a container for the journal events and attachments. This option can be a good choice if there are specific fields that need to be associated with each journal entry, and if these fields are not available in the existing activity entities.

Option C: One custom table with an additional Attachment column This option involves creating a custom table with an additional attachment column to store all the journal events and attachments. With this option, the custom table stores all the journal entries as records, and the attachment column allows customers to attach multiple files to each journal entry. This option can be a good choice if there are many fields associated with each journal entry, and if the existing activity entities in Dataverse do not meet the needs of the journal events.

Option D: One activity table with an additional Attachment column This option involves adding an attachment column to an existing activity table in Dataverse to store all the journal events and attachments. With this option, each journal entry is stored as a record in the activity table, and the attachment column allows customers to attach multiple files to each journal event. This option can be a good choice if there are specific fields associated with each journal entry, and if the existing activity entities in Dataverse meet the needs of the journal events.

Option E: One custom table with enabled attachments option This option involves creating a custom table with enabled attachments option to store all the journal events and attachments. With this option, the custom table stores all the journal entries as records, and the attachments option allows customers to attach multiple files to each journal entry. This option can be a good choice if there are many fields associated with each journal entry, and if the existing activity entities in Dataverse do not meet the needs of the journal events.

Option F: One virtual table with an additional Attachment column This option involves creating a virtual table with an additional attachment column to store all the journal events and attachments. With this option, the virtual table acts as a container for the journal events and attachments, and the attachment column allows customers to attach multiple files to each journal entry. This option can be a good choice if there are specific fields that need to be associated with each journal entry, and if these fields are not available in the existing activity entities.

Based on the requirements of SeeTheWorld's travel journal functionality, Option A, One activity table with enabled attachments option, can be a suitable option as it allows the creation of a single table to store all the journal events with an enabled attachments option. Customers can attach multiple files to each journal event, and this option takes advantage of the existing activity entities in Dataverse. However, it is essential to review the specific needs of the journal events to determine the best option.