D365FO and Sharepoint integration issue on dev box: "You are not authorized to connect to 'https://sharepoint.sharepoint.com/

Troubleshooting SharePoint Integration After Upgrading D365FO to Version .42

After upgrading to Dynamics 365 Finance and Operations (D365FO) version .42, we encountered an issue with all of our SharePoint integrations. Here's a step-by-step guide on how we identified and addressed the problem.

Verifying the D365FO and SharePoint Connection

To verify the connection between D365FO and SharePoint, we navigated to the Document Management Parameters section. From there, we selected SharePoint and clicked on Test Interactive Connection to check the connectivity status.

Unfortunately, we received the following error message:
"You are not authorized to connect to 'https://sharepoint.sharepoint.com/'."

This error prompted us to open a support ticket with Microsoft to further investigate the issue.

Microsoft’s Response and Solution

Microsoft's response highlighted an important distinction regarding development environments. They clarified that:

"For development purposes, a Unified Development Environment (UDE) will work. However, this will not work in a regular cloud-hosted environment. So, if there is a need for active development with SharePoint, a UDE is the recommended approach."

What is a Unified Development Environment (UDE)?

A Unified Development Environment (UDE) is a specialized development environment designed for working with Finance and Operations apps, such as Dynamics 365. It allows seamless integration with SharePoint for active development and testing. However, it's important to note that the standard cloud-hosted environment does not support the same level of integration for development purposes.

Conclusion

If you are facing similar issues with SharePoint integration after upgrading D365FO, it may be due to the environment you are working in. For active SharePoint development, consider switching to a Unified Development Environment to ensure smooth connectivity and integration. If you’re using a cloud-hosted environment, you may encounter limitations as we did.

For more information on using UDE and troubleshooting D365FO integration, visit Microsoft’s official documentation on Unified Developer Experience for Finance and Operations Apps.

How to Import D365FO Packages Using Postman and the Data Management Package REST API -- X++ --D365FO Packages import

 

Introduction:

In this blog, we'll walk through the process of importing a D365FO package using Postman. We will focus on how to use the Data Management Package REST API, providing the necessary steps to configure and send your requests. Additionally, we will explain how to access container files stored in Azure Blob Storage using Postman.

1. D365FO Package Import Using Postman

To import a package in Dynamics 365 for Finance and Operations (D365FO), we utilize the Data Management Package REST API. Here's how you can do it:

API Endpoint

The endpoint to use for importing a package is:

https://BALI.Dynamics.com/data/DataManagementDefinitionGroups/Microsoft.Dynamics.DataEntities.ImportFromPackage

For more details on using the Data Management API, check out the official
 Data Management API documentation.

2. Authorization

Before you can interact with the API, you'll need to authenticate your requests. The authentication is done via a Bearer Token.

Authorization Header

• Key: Authorization

• Value: Bearer <YourToken>

You can obtain the token by registering your app in Azure Active Directory and using the OAuth 2.0 flow to retrieve the token.

---

3. HTTP Request Headers

You need to set the following headers for your HTTP request:

• Content-Type: application/json

4. Body of the Request

In the body of your request, you need to provide the necessary details in JSON format. Here is an example:

 {

  "packageUrl": "https://BALIBlob.blob.core.windows.net/saleslines/%74297-B72F-814249C6D103%7D%20",

  "definitionGroupId": "imp salesline",

  "execute": true,

  "overwrite": true,

  "legalEntityId": "BALI"

}

 

 

Parameters Explained:

packageUrl: The URL of the package file stored in your Azure Blob Storage. This is the URL where your package file is located.
definitionGroupId: The ID of the Data Management Definition Group you are importing.
execute: A boolean flag indicating whether to execute the import after uploading.
overwrite: A boolean flag indicating whether to overwrite existing data during the import.

• legalEntityId: The ID of the legal entity associated with the data import 

5. Accessing the Package URL from Azure Blob Storage

The Package URL refers to the location of the package file that is stored in Azure Blob Storage. Here’s how to retrieve it:

1. Log in to Azure Portal.

2. Navigate to your Storage Account: Go to the Azure Storage account where your package file is stored.

3. Select your Blob Storage: Choose the "Blob Service" and navigate to the container where the package is stored.

4. Access the Container: Click on your container, and you’ll see a list of files.

5. Select the Package File: Click on the package file you want to import.

its this is D365FO datapackage (exported from d365FO do needfull changes in data package and upload it to container) 

once we have container file URL we can access this from Post man

Conclusion

By following the steps outlined above, you can easily import data packages into Dynamics 365 for Finance and Operations using Postman and the Data Management Package REST API. With the flexibility of Azure Blob Storage for storing your files, this process streamlines data management in D365FO.

For more detailed guidance on using the Data Management API in D365FO, visit the official Microsoft documentation.

Preventing Price Recalculation for Imported Sales Lines ( custom price other then trade agreements price) in D365FO - X++ - Microsoft Dynamics 365 Finance & operations

 In D365FO if sales line is imported from excel using custom built solution or sales line is created from Code X++ and user provide its own unit price (price other then trade agreements) after sales line creation user go to sales order and click Recalculate and update the Unit price as per trade agreement. To stop this behavior (stop recalculation) if price is enter manually or is custom price is imported for sales line

need to add below code after you modify price in code 

Salesline.setPriceDiscChangePolicy(PriceDiscSystemSource::ManualEntry, fieldNum(Salesline, SalesPrice));

it will stop recalculating price for particuallar sales line when some one click Recalculate button on sales order 

D365FO. Dynamics 365 fiance and operation. Get and update contract of batch job on Controller run method. ax 2012

set Batch id in contract if batch isInBatch check is true

in run method we will update the contract and set the batch id.


class BrFunctionalLocationRecordsController extends SysOperationServiceController
{
    protected void new()
    {
        super(classStr(BrFunctionalLocationRecordsService), methodStr(BrFunctionalLocationRecordsService, functionalLocationRecordsService), SysOperationExecutionMode::Synchronous);
    }

 
    public static BrFunctionalLocationRecordsController construct(SysOperationExecutionMode _executionMode = SysOperationExecutionMode::Synchronous)
    {
        BrFunctionalLocationRecordsController      controller;
        controller = new BrFunctionalLocationRecordsController();
        controller.parmExecutionMode(_executionMode);
        return controller;
    }

 
    public static void main(Args _args)
    {
        BrFunctionalLocationRecordsController controller;
        // to update contract value at main we can initialize contract here.
        //BrFunctionalLocationRecordsContract   brFunctionalLocationRecordsContract;

        controller = BrFunctionalLocationRecordsController::construct();
        //and can set contract values here
        //brFunctionalLocationRecordsContract = controller.getDataContractObject();
        controller.parmArgs(_args);
        controller.startOperation();
    }

 
    public ClassDescription defaultCaption()
    {
        return "@Br:FunctionalLocationRecords";
    }

   
    public void run()
    {
        BrFunctionalLocationRecordsContract brFunctionalLocationRecordsContract;

       //getting batch contract.
        brFunctionalLocationRecordsContract = this.getDataContractObject();
       
        Batch                                   batch;
        if (this.isInBatch())
        {
            //getting batch information;
            batch = this.currentBatch;
            //setting batch id in contract
            brFunctionalLocationRecordsContract.parmBatchHeader(batch.BatchJobId);
        }
        super();
    }

}

Upload Files To Azure BLOB From D365 FO

Uploading attachment file to Microsoft azure storage account blob.

1.           Goto https://portal.azure.com
2.             Goto Storage Account
   
3. Click on Add 

   
   
   
4. Fill details and click Review + Create
   
5. Click on create. It will deploy the storage account.
6. Go to newly created storage account go to access key .
   
   Key 1 and key 2 or connections strings will be used to access this storage account.
   
7. Go to container and click Container
   
8. Fill the name and click ok.
   
9. Now we will create new runnable class in D365FO to upload file to newly created container.
   using Microsoft.WindowsAzure.Storage;
   using Microsoft.WindowsAzure.Storage.Blob;
   
   
   class UploadFileToAzureBlob
   {
   
   
       public static void main(Args _args)
       {
           DocuRef     docuref;
           /*const str connectionString =  "";*/
           const str containerName = "selflearningcontainer";
           str storageAccountName = "selflearningtest";
           str key = "”;
   
   
           System.IO.Stream attachmentStream = null;
           try
           {
   var storageCredentials = new Microsoft.WindowsAzure.Storage.Auth.StorageCredentials(storageAccountName, key);
   CloudStorageAccount storageAccount = new Microsoft.WindowsAzure.Storage.CloudStorageAccount(storageCredentials, true);
           
               if(storageAccount)
               {
                   CloudBlobClient blobClient = storageAccount.CreateCloudBlobClient();
    CloudBlobContainer blobContainer = blobClient.GetContainerReference(containerName);
                   blobContainer.CreateIfNotExistsAsync();
   
   
                   changecompany('USMF')
                   {
                       SalesId salesId = '001835';
                       SalesTable SalesTable;
                       //SalesTable salesTable = SalesTable::find(salesId);
                       select SalesId from salestable where SalesTable.salesid == '001835';
               
       select firstonly docuref where docuref.RefTableid == salesTable.TableId
                       && docuref.RefRecid == salesTable.RecId;
                   }
   
   
                   if(docuref.isValueAttached())
                   {
                       docuValue = docuref.docuValue();
   
   
   CloudBlockBlob blockblob =    blobContainer.GetBlockBlobReference("testingblob");
                       if(blockblob && !blockblob.Exists(null, null))
                       {
                           var storageProvider = docuvalue.getStorageProvider();
                           if(storageProvider != null)
                           {
    var docContents = storageProvider.GetFile(docuValue.createLocation());
                               attachmentStream = docContents.Content;
   
   
                               if(attachmentStream)
                               {
                                   blockblob.UploadFromStreamAsync(attachmentStream).Wait();
   
   
                                   blockBlob.FetchAttributes(null,null,null);
                                   BlobProperties BlobProperties = blockblob.Properties;
                                   if(BlobProperties.Length == attachmentStream.Length)
                                   {
                                       info("file uploaded successfully");
                                   }
                               }
   
   
                           }
                       }
                       else
                       {
                           info("file already exists");
                       }
                   }
               }
               else
               {
                   error("unable to connect azure file storage with the provided credentials");
               }
           }
           catch(Exception::Error)
           {
               error("Operation cannot be completed");
           }
           
       }
   
   
   }
   
   
10. Now we will run the class 

Trigger logic App from D365 Part 2

In this part we will see how to trigger logic app form D365FO (Dynamics 365 For operations)

For logic App details visit Part 1 

Create a class name :LogicAppHelper
with method : callPostWebAPI

class LogicAppHelper

{

    #define.ApplicationJson('application/json')

    public boolean callPostWebAPI(URL _serviceOperation, Comments _postData, str _header ='')

    {

        RetailWebRequest request;

        RetailWebResponse response;

       

        boolean ret;

        ListEnumerator  listEnmr;

        List dataList;

        RetailCommonWebAPI webApi = RetailCommonWebAPI::construct();

   

        try

        {

            response = webApi.makePostRequest(_serviceOperation, _postData, _header #ApplicationJson);

        }

        catch

        {

            ret = false;

        }

   

        return ret;

    }

}

Now we will create runable class (job)

class LogicAppConnectionJob

{        

    /// <summary>

    /// Runs the class with the specified arguments.

    /// </summary>

    /// <param name = "_args">The specified arguments.</param>

    public static void main(Args _args)

    {    

        LogicAppHelper  appHelper = new LogicAppHelper();

        container       conValues;

        AccountNum custAccount;

        str             callingparam ;

        ;

        

        custAccount = 'US-001';

        callingparam  = "{'CustomerAccount':'" + custAccount +" '}";

       //appHelper.callPostWebAPI(URL ,Comments,_header) 

       // URL : URL generated while creating logic for details see part 1

       // Comments: passing customer account to logic app as JSON Schema for details see part 1

        appHelper.callPostWebAPI('https://URL-Generated-By-Logic-App-Response-Receiver' ,callingparam);

    }

}

hopefully this will help you all...

GOTO PART 1

Logic App For Dynamics 365 for operation (D365FO).Azure logic App (part 1)

Summary :

In this part we are going to create Logic App for Dynamics 365 For Operations.in this we will see how we will send email using logic app.

As we know right now there are no triggers for D365 FO, so we will achieve this using http response receive.

In this part we will discuss

a)      Login azure portal.

b)      Create Resource for logic app.

c)      Create basic logic app 

d)      And trigger logic using post man 

Part 2

  

Step 1:

Sign in azure portal

https://azure.microsoft.com/en-us/account/   

Step 2:

After log in, go to Create a resource à Web à Logic App

Step 3:

a. Enter logic app name e.g DemoLogicApp.

b. Select Subscription.

c. Check Create new in resource group.

d. Enter resource group name like DemoResourceGroup

e. Select location

f. Click on create.

Step 4:

Click All services
filter by Logic App

Step 5:

Click DemoLogicApp

It will open logic App Designer

Select Blank Logic App

It will look like 

 Step 6:

First we will add trigger to logic app(trigger is the point which define when to execute logic app)

 a)      Search for logic app trigger (When a Http Request is Recevied)

 b) Select When a Http Request is received 

  

 c) Now add Json Schema: 

Step 7:

a)  Now we will add action. Click next step

    b) Search for send email action

    c) Select Office 365 Outlook

   d)  Select send Email

 e)  Now we will sign in to office 365 Outlook.

  f)    Fill details

a.       Add to account

b.      Subject

c.       Body (you can add customer account which was define in jSon Schema.

Step 8:

Click on save

It will generate Https url

  Step 9:

        a)      Go to post man

        b)      Select post

        c)       Enter url

d      d)  Go to header tab add key and value 

    e) Go to body and define body (we defined json Schema in logic app)         

    f)  Click on send

    g)  Go to logic app àOverview à click refresh

We can see the status is succeeded which mean logic app got triggered and send email successfully 

in next part we will discuss how to connect D365 with logic apps 

Part 2 in this part we will discuss how to trigger Logic App From D365