Switch legal entities in D365F&O, using Copilot

 


Amigos, use this cool hack to or switch between legal entities, using Copilot sidecar chats.

For example, when we ask the Copilot: to change the legal entity, here is the response that we get:


Unimpressive, eh? It's replying by saying the steps to change between legal entities, embdedding the links from Microsoft learn. 

Now, let us bring some life into it.

Log on to: https://copilotstudio.microsoft.com/ and choose the correct environment from the dropdown:


Choose from Agents >> Copilot for Fiance and Operations apps:


This is where you can define topics, actions, knowledge, Activities and a lot of other staffs that can contain the overall behavior of Copilot chat. 

Click on Topics >> Add a topic >> Choose Topic from the Blank:


  This is where you would land:


Start by giving a proper name to your chat topc:


In the Phrases >> Edit >> add prompts like this:


In the + symbol from below, select Add a question :


Frame your question like this:


From the Identify option, choose the following: Organization as an answer:

Which means when the user responds to the question, the system should identify it as an Organization.

Change the name of the variable as company:



Which enforces the variable to be used as a Global variable, instead to be scoped only to this step.

In the next step, declare a variable like this:



Create the variable as:



And give the name like this:


In the To value, give the value like this:



Which is the base Url of your F&O instance (please note: keep it like this: https://org0d99e1f5.operations.dynamics.com/?cmp= and not the compplete URL). To this, the variable baseUrl, automatically identifies itself as of type String.

Set another variable shown as above:


And name it as: completeUrl. Then click on the Set value >> click on Formula:


Give the formula like this: 


Which is essentially concatenating the selected variable at the end of the bas URL.

Click on Insert to continue.

Lasly click on + sign and add: Send message:


Here you go and click on fx button to formulate the messgae:


You need formulate the result much like this:


That is going to convert the answer as a Link, with the company name on it. Click on insert, Save your topic and Publish it, by click on the 'Publish' link from the top.

Let us come back to our D365F&O and reload the Copilot chat, and ask the same question. Let us see what the result comes this time:






The legal entity comes as a hyperlink, clicking which would take you to the desired legal entity.

Cool, nah? Let me take your leave for today. Would come back soon with more such cool hacks from Copilot. Till then, take care, much love and Namaste as always 💓💓💓


Comments

Post a Comment

Popular posts from this blog

Make your menu items visible on main menu, conditionally,, using this cool feature of D365FO

Image
  Wassup guys? I am sure you must have encountered this situation where you needed to display your menuItems, on main menu, based on some condition, haven't you? This was only possible by using config keys and flights. Things get a bit tricky,  when suppose you have a requirement like this: you need to make it dynamic, by introducing a toggle switch on a field on a paremeter form.  Suppose on Accounts Receivables Parameters >> You have a field called ' Show US customer '. You have a requirement that says when you turn on this toggle, then only the menuItem ' Input SSN details ', under AR module. This is now highly acheivable by leveraging subscription to 'SysMenuNavigationObjectFactory' class, simply by saying a. Create a new class USMenuItemsVisibilityManager b. Copy the following method, with proper documentation (don't change signature/anything else) [SubscribesTo(classstr(SysMenuNavigationObjectFactory), staticdelegatestr(SysMenuNavigationObjec...
Read more

X++ : mistakes which developers commit the most

Image
   The most important thing is to remember where and when to write the code. a. Developers have an inherent habit of writing erratic select statements: select * from custTable where custTable.AccountNum == <SomeValue> Where in essence we need to make use of optimized choice of fields in the select statement. b. Making use of 'continue' keywords: While select custTrans where <someConditions> { if (cusTTrans.CustGroup != mappingTable.CustGroup) { continue; } } 'Continue' statements are precisely a very unhygienic way of designing your code. The above statement could have been easily ornamented by using exists/not exists joins. Using Continue statements would eventually result in a high performance impact. Also select statements should be made punctuated with a 'firstonly' clause -- just not from best practise standpoint, but also from performance considerations. c. Writing nested loops: This is a common mistake that perha...
Read more

Are you still using macros? Be sure you read this.

Image
  You still use a lot of macros in your code, don't you? Of course you should: Macros, as per Microsoft,  are p recompiler directives are processed before the code is compiled. The directives declare and handle macros and their values. The directives are removed by the precompiler so that the X++ compiler never encounters them. The X++ compiler only sees the sequence of characters written into the X++ code by the directives. However macros, are not quite recomended by Microsoft. They are slow, they can be subsequently deorectaed at any later time.  The Macros are  actually  a type of classes, only that they are not instantiated and not need be defined as classes. Hence runtime garbage collection could be a huge issue, consquently (a class when gets out of scope, gets garbage-collected owing to the destructor classes of DOT net instrumentation classes). Summing up, macrros are a bit old way of writing code. Use static classes instead. public static class MyIdenti...
Read more