When working with Date and Time fields in Dataverse, one of the most confusing parts is how values are stored in the backend vs. how they are displayed to users
When working with Date and Time fields in Dataverse, one of the most confusing parts is how values are stored in the backend vs. how they are displayed to users
Picture this: You’re on the road when you get a notification that someone new just subscribed to your newsletter. You want to know more about this reader: are they engaging
Kick off a hands-on series on Copilot Studio for Dynamics 365 F&O. See what it is, the setup you need, how it uses Dataverse, built-in copilots, and two X++ extensibility
Today I’ve decided to do with AI a test that I’ve never done before: creating an Azure Logic App workflow that uses a connector, more specifically the Business Central connector.
If you offer multiple email topics or purposes, there’s bound to be some overlap. But promoting Purpose B to someone already subscribed to Purpose B? Not a great look. In