We have several data time field that are being exposed in the Dataverse on virtual entities that are flowing in from an on-premises SQL database. These columns have been set to 'Date Only' and time zone independent and are displaying correctly in our model driven app as well as in the Dataverse. However, in Power Pages, these fields all display as being one day earlier than they should be. For example, in the Dataverse a birthdate maybe '7/12/1955' but in the Power Pages web page that displays the basic form, that same date will be shown as '7/11/1955'. Looking at the element in Edge Dev Tools shows that value data is correct, and the data-behavior attribute is set to 'TimeZoneIndependent'.
Any thoughts from the community on what could be done to correct this, other than creating a nvarchar field to hold the date as a string in the SQL database?

Report
All responses (
Answers (