[quote user="S.Kawamura"]
Hi,
I think BC license is required to access Timesheet data.
A workaround that comes to mind is to prepare a table on Dataverse with the same structure as BC timesheet and synchronize it with BC's timesheet data.
The Dataverse connection feature enables data synchronization between BC and Dataverse for some tables, such as customers and suppliers, as a standard feature.
In this case, the user needs a license to access Dataverse, but does not need a license for BC.
However, timesheets are not included in the standard synchronizable tables and require customization.
I hope this helps you.
S.Kawamura
[/quote]
This is not complaint with the license guide. In the scenario described here using Dataverse. You will still need at least a team member license:
Dynamics 365 licenses are required for users or devices that directly input, query, or view data from Dynamics 365. Similarly, licenses are required for users or devices that input, query, or view data from Dynamics 365 through a pooling device. Pooled connections use a non-interactive Dynamics 365 user account (or application access in Business Central) that can access the system but only via the web service layer. Internal users and devices accessing Dynamics 365 data indirectly through a portal or via an API to a separate service (such Microsoft Outlook) must also be properly licensed, regardless of whether they are set up as a Dynamics 365 user for the service. For example: Dynamics 365 Licensing Guide | August 2022 P a g e | 45 • Any user or device that accesses the service, files, data, or content provided by the service that is made available through an automated process requires a Dynamics 365 license. • The number of tiers of hardware or software between Dynamics 365 and the ultimate user or devices does not affect the number of licenses required.
