While working on a recent project to replace a low code platform with the Power Platform, one of the requirements that we had was to replace some of the Excel export and import functionalities that the existing system had to be able to send large Excel files into various other systems to be analyzed and consumed.
Up until recently the email description field or the body of the email have been stored within the Microsoft Dataverse data store. This is going to be changing in the coming months where the email description field will be moved to an Azure Blob Storage
I have been working with a client for the past year or so, where they have been using the Data Export Service to write data from their Dataverse environment to an Azure hosted SQL Server.
It seems like this was only a few days ago, but based on the sample that was published by Microsoft it’s been almost 2 weeks since Microsoft released CRUD support on Virtual tables.
Since the announcement by Microsoft at the Microsoft Business Applications Summit last month, and even before, I’ve been eager to take a look at the new SQL Connection for the Common Data Service Endpoint. What this means is that we can not write and execute SQL queries against the entity data.
In this blog post I will demonstrate how to use Azure Service Bus and a Listener application to integrate between the Common Data Service (Dynamics 365 or Power Apps Model Driven Application) and an On Premise SQL Service database.
The preview version of SSDT for Visual Studio 2017 (15.3.0 preview) is now available. This release introduces a standalone web installation experience for SQL Server Database, Analysis Services, Reporting Services, and Integration Services projects in Visual Studio 2017 15.3 or later.
Recently we have encountered an issue where a domain admin (and local admin) account was trying to access the SSRS Report Manager and Report Server web sites and was getting the following error:
User DOMAINUserAccount does not have the required permissions. Verify that the permissions have been grated and Windows User Account Control (UAC) have been addressed.
Visual Studio 2010 and Report Builder 3.0 RDL reports use a new schema that is not supported by SQL Server 2008 Reporting Services. They are designed to work only with SSRS 2008 R2. Currently there is no way to publish a VS2010 Report on SQL Server 2008 without some modifications to the RDL code.
This issue sometimes happens when you deploy a web application that contains report files on IIS7.
The reports work fine in the development environment, but once published nothing appears in the results.
