Dynamics 365 for Talent – Integrations

Few days ago, I’ve started with a story about new product (still Technical Preview) – Dynamics 365 for Talent. I want to spend a few words about possible integrations.

When you look at the official announcement, you can find that key integrations will support the overall business and the following integrations will be created, but they will be available at or shortly after general availability:

  • LinkedIn
  • Microsoft Dynamics AX 2012 R3
  • Microsoft Dynamics 365 for Finance and Operations, Enterprise Edition
  • Background screening
  • Global payroll providers
  • ATS providers

As you can see, there are not planed integration with Dynamics 365 for Financials or with Dynamics NAV. But  think it will be necessary because these products don’t have a real HRM solution. But I’ve also found that it will be possible to use Common Data Services platform with built-in extension points for Power Apps, Flow and Power BI.


But, when I tried to make connection via Flow and Power App, I’ve found that it is still not available as a connection. Of course, it is probably because it is only technical preview and I’m sure it will be available with a general availability. I’m waiting this moment and I want to make some kind of integration. I’ll write about it, I hope soon.


Posting Groups in Assembly Order in NAV

In my previous articles about using of posting groups in Dynamics NAV, I didn’t describe using of posting groups in Assembly Orders. Assembly Orders are here in the few last versions of NAV and I want to show them as well.

Using of Assembly Orders is not so complex and we can use only Items on header and Items and Resources in lines. Because of that, we can use only Inventory Setup and General Posting Setup. You can see the flow chart with description of usage these posting groups:


When we post one Assembly Order, we will get the following G/L Entries:


Posting Groups in Service Management in NAV

I’ve already wrote 27 articles about using of Posting Groups in NAV. Now, I’ll continue this series with the new topic – Service. When we use Service Order, all posting will be based on the following flow-chart:


You can notice, this is very similar with postings in Sales, but we have some specifics about using of additional fees. But if you look at the part based on Service Lines, everything is the same. I want to accent that this part is drawn for items ()because of usage Inventory Posting Group and Location); if you use G/L Account or Resource, there will not be inventory postings.

Now, let look at the posting results. First, if we decide to post “Ship and Consume” from Service Line, that means these lines have been used for servicing but cannot be included in the invoice to the customer and we will have only inventory postings if we used items (in other cases, we will not have anything for posting):


But if we decide to post “Ship and Invoice” from Service Line, the result will be different. In this case, we have some additional entries except inventory posting:


And on the end, we need to finish posting from Service Order. If we have not some additional fees for invoicing, it will not be anything for posting, but if we have additional fees, it looks the same (for “Ship and Consume” and “Ship and Invoice” examples):



Posting Groups #19 – FA Sales Credit Memo Posting

It is usual to have possibility to post Credit Memo for any item you sold. You can also make Credit Memo for Fixed Assets you sold. Generally, you can use the same flowchart about using of posting groups, as I published for FA Sales Posting.

But G/L entries will not be the same (with opposite sign) as you got in FA sales posting process. You will get the following G/L entries:


Entries are a bit different in comparison with posted invoice. Entries in FA Ledger Entries also will be the different. You will get only Gain/Loss FA Posting Type entries in FA Ledger Entries with Credit Memo Document Type. That means, you must create additional Acquisition and Depreciation entries manually, if you want to have Fixed Asset again in your system.