How to Build Power Portal connected with Business Central

Introduction

When I think about new Dynamics 365 Business Central (in the future, I’ll use only ‘Business Central’ or just ‘BC’) features, the first things in my mind are openness and integrations. Then one of the most common limits in Business Central (and in Dynamics NAV before) was lack of portal connected with the database. Of course, you could develop portal from the scratch or use one of existing solutions and develop integration… But what is common in both of these cases? You need to pay in the first case for development (not so cheap) and in the other case for IP or license (again not so cheap).

But with Power Platform we got something more. Now we have Power Portal and as you have Power Platform included in your user’s subscriptions, you don’t need to pay something more (minimum, not such a big amount of money). Only what you need to pay is using portal, but this is really not so costly (100USD per month for 100,000 page views for unauthenticated users or 200USD per month for 100 daily login sessions for authenticated users. More details here: https://powerapps.microsoft.com/en-us/pricing/). And yes… we have an issue here… Power Portal is based on Dataflex Pro (formerly known as Common Data Service). But this is an opportunity, not a limitation. And this is the topic of this whitepaper.

Start with building entities in Power Platform

First as I already mentioned, this is necessary to build solution in Dataflex Pro and that means you need to create entity(ies) you want to connect with Business Central. That means you need to run Power Apps: https://powerapps.microsoft.com/. After that, I’ll continue with task. In this example, I’ll use Employee entity as we already have Employee table in BC.

To do this, you need to start from Entities (Data > Entities in the left navigation pane) or you can start with Solutions and create new entity from there. In the new entity, enter Display name and enter primary name.

Click Done when you enter that. After that, you need to add new fields using Add fields command. When you finish with all fields, click Save Entity to save all changes.

When you finish with all details in creation of entity you can start with building connection with Business Central. But keep in the mind that you need to make something more here and we will come back later. Right now, only one thing you can add is Key just to avoid having duplicates and my recommendation is to copy keys from BC table.

Connecting Business Central with portal

OK, connection with the Business Central can be done on a few different ways and I’ll try to explain all of them here.

Business Central customizing an integration with Common Data Service

From the Wave 1 2020, Business Central supports an integration by default with a set of entities in the Dataflex Pro default database, but you can make customization through extension and add more. For developing extensions that integrate Business Central with Dataflex Pro, system uses extensibility capabilities where proxies to Dataflex Pro tables can be created in Business Central, and these will be made extensible. This allows for custom attributes to be synchronized and for additional tables to be added to the default synchronization process.

When you create this extension, only what you need to do is mapping tables with entities as well as mapping fields in Business Central and Dataflex Pro.

I don’t want to write in details how you can do it as Microsoft already published completely documentation how to build this kind of extension and how to configure it. For more details, open this page: https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/administration-custom-cds-integration.

When you finish with developing an extension, you can find here how to map tables and fields: https://docs.microsoft.com/en-us/dynamics365/business-central/admin-how-to-modify-table-mappings-for-synchronization.

When you connect entities in Dataflex Pro and Business Central, you can continue with building Power Portal.

Integration using webservices and Power Automate

Previous way of integration is native, but it requires some development knowledge. But what if you are not developer and still want to build portal based on Business Central? Do you think it is possible? Yes… this is an answer.

From the Entity page in Power Apps, just click Get Data and in the Power Query window choose OData tile. Go next and then you need to stop yourself there. You should move to the Business Central. Open Web services page and add page you want to use in synchronization. In our case, this is page 5200… just click New, as Object type choose Page and add this page number; enter Service name you want to use and click on Publish field. Copy OData V4 URL value.

Move back to the Power Apps and in the Connection setting paste this value to the URL field. Choose Organizational account as an Authentication kind. Confirm your credentials and go to the next page. Click Next until you open the following page.

Now you need to choose Load to existing entity option and in the Destination entity choose entity you created (in my example BCEmployees).

In the Field mapping part of window (right side), you need to map fields from web service in Business Central as a Source column with Destination fields (fields in our entity). When you finish it, just click Next and you will find a page where you can configure refresh settings. That means you need to choose how often system will synchronize data from Business Central web service to the entity. Click Create and you have been finished with integration.

But something will miss here. As you are using just refresh model, that means you will get records from Business Central, but you cannot insert there. Actually, you can insert to entity, but system will not insert them to BC. To solve this, you can create very simply flow in Power Automate. Actually… you will need as many flows as you want actions.

You can see on previous picture that I chose When a record is created and it will be OK if you want to have only Insert from portal. But if you want more action, you need to use the following triggers:

  • For ModifyWhen a record is updated,
  • For DeleteWhen a record is deleted.

In this example you will see flow for inserting, but I think you can easily understand how to create two additional flows based on well-known parameters.

Keep in the mind that you need to use the following parameters in the trigger:

  • Environment – choose an environment you used for building solution in Power Apps
  • Entity name – entity you created
  • ScopeOrganization

Now when you save it, your solution is finished. I would just like o mention that instead of web service integration you could choose API integration as well:

Configuration in both of cases is very similar and there is not a reason to repeat completely process.

Building a portal

Power Portal

Now when we made an integration using one of the models, we can continue with building our portal.

To finish with this process, we need to open Power Apps again and to start with creation new Power App. You can start from Home or from Create and you need to choose Portal from blank option.

Enter the name of your portal and carefully choose Address for your portal. This is place where you can also choose a language.

When you select Create, you need to be ready to wait some time until system create portal. It usually takes a few minutes, sometimes more, sometimes less… but be a patient. When an app is created, open it in the edit mode. You will see we have prebuilt portal, but we want to add new page with our data. To do this, select New page and choose Blank.

System will create new blank page and we need to add necessary components. Select Components icon in the left-side menu and locate List. This is logical if you want to start with a list view.

Now you need to configure some details. As we will create new component, choose Create new display and as Entity choose your entity (BC Employee in my example). The next important step is to choose a view as each entity has more views. I think that Active {items} are logical choice here.

OK, this is how we can create a list. But if you want to have possibilities to create new entry or to edit or delete it from here, you have an opportunity to do it immediately here. In the right-sided pane you will see a few options appear.

You can choose if you want to add the following features here: creating, viewing, editing and deleting. If you switch-on any of these options, you will get an opportunity to choose which form will be run to make this action. This is very easy for configuration, but what is important is that you need to have these forms already built.

OK, now you need to select Sync Configuration command to see result. But you can see that you have only two columns here in your list and this is not what you want. This is because, when system creates entity, views are created automatically but only with the main field plus Created On. But this is not problem as you just need to customize your view.

View customization

To customize view, you should go back to Power Apps and entity you previously created. There you need to select View tab and from the list of all view to select one you want to customize. In our case it is Active BC Employees.

When you open this view in edit mode, you need to add fields you want to see on your view. I’ll add Name, Surname, Address and City and resize it as I would like to see on the screen.

When you finish with adding and/or moving fields, you need to click first Save and after that Publish commands. Keep in mind that if you didn’t publish it you cannot use it.

Test

Now we can say we finished with everything. Go back to the Power Apps and choose Apps on the left-side pane. You will see completely list of your apps. Just choose app (portal) you just created. When you run it, choose the page we created and that’s it. You can see the window in portal with our data from Business Central.

What happened with CDS and what’s the hell is Dataflex?

Two days ago when we started with Microsoft Inspire, Charles Lamanna published new blog post about Introducing Microsoft Dataflex, a new low-code data platform for Microsoft Teams. But he also announced that Common Data Service has now been renamed to Microsoft Dataflex Pro… and everybody were confused.

What happened with CDS, what is Microsoft Dataflex and what is difference in comparison with Dataflex Pro? Many of people went to Wikipedia and found DataFlex there…

I will try to avoid any additional confusing on this topic and try to be very short and very clear.

First, DataFlex you found on Wikipedia doesn’t have anything with Microsoft Dataflex (& Pro). You can go there and read what it is, but this is not my topic.

As the second fact, Microsoft Dataflex Pro is Common Data Service. Nothing more and nothing less. This is just rebranding. You can see that we still have old URL with common-data-service there. If you know CDS, you will know Dataflex Pro. If don’t, you can find a lot of materials on Microsoft learning site… and I’ll highly recommend starting to learn it if you are doing with Microsoft BizApps.

As this rebranding can confuse, I tried to create one timeline with all these changes. I’m not 100% sure I didn’t miss something, but it will be more then enough to understand what happened here.

And not as a third topic – Microsoft Dataflex (without ‘Pro’). What it is and what it isn’t? This is built-in, low-code data platform for Teams, and it is built atop the Common Data Service (or to use new name, atop the Microsoft Dataflex Pro 😊). This tool will help Teams users to easily build custom apps inside. You will not need to leave Teams and to build everything inside it with really user-friendly UI. You can build apps using Dataflex as environment and together with Power Apps, Power Automate and Power Virtual Agents. And this is not full CDS… this is just a subset of Dataflex Pro capabilities and usage is limited to within Teams.

As I said I’ll be short, I don’t want to write details about it and I’ll just recommend to read Charles Lamanna blog post about it and to find some good presentations on Microsoft Inspire digital event: https://powerapps.microsoft.com/en-us/blog/introducing-microsoft-dataflex-a-new-low-code-data-platform-for-microsoft-teams/.

How to integrate Business Central with Dynamics 365 Talent – part 2 (configure BC & Talent)

If you’ve already read my previous article about introduction in BC and Talent integration, then you probably expect the next part. I cannot put everything in one blogpost as it will be a huge one and it can be confused to track all details, so I decided to write it in parts. Today, I’ll write how to prepare Business Central and Talent and how to locate data/entities you will handle with.

As I’ve already mentioned in previous post, as we don’t need all HR capabilities in Business Central and we will use all of them in Talent, we will enter data directly to Talent and move to BC only data necessary for other areas in BC. We will move data to Employee table as this table will be used in other parts of BC.

As we will create new employees in Talent, we need to configure No. Series to be fit with Talent requirements. If you want automatic numbers, you need to be careful and to make it exactly the same as in Talent, but I’ll recommend to configure Employee number series as Manual Nos.; this will keep the same numbers in Business Central as we have in Talent and you will avoid all potential risks.

As connectors with Business Central, we will use API’s. Employee table, for example already exists as an API, but if you would like to connect something more, you will probably have to create custom API and custom connector.

What we can synchronize? As I said, minimum we need in BC is Employee table. And you need to find entity as a source in CDS (I’ll explain later). You can connect entities as following:

Business CentralTalent / CDSBC API
EmployeeWorker …employee
Alternative AddressWorker Addresscustom
QualificationSkill Typecustom
 

If you want to find all details about Workers data in Talent, the best is to use the following Worker entity relationship model. But the best is to integrate only what is really necessary… only what you will really use in Business Central.

As we need to locate Talent entities, you need to open list of CDS entities in PowerApps platform (you don’t need to do nothing in Talent environment and you can use it only if it will help you to better understand environment; for all integration purpose you will use CDS – PowerApp). When you open PowerApps web page, you need to choose environment created for Talent.

After that, you need to open Data and Find Entities. In Entities, you can easily find Worker entity as this is a place where we can find our information.

Opening this entity, you can address all necessary fields you want to use in integration. And how to do it, you will see in the following post.

How to integrate Business Central with Dynamics 365 Talent – part 1 (Introduction)

When I think about new Business Central features, the first thing in my mind is openness for integrations. As a part of Dynamics 365 family, the main power of this solution is when it can work simultaneously with other. Because of that, I showed these capabilities in a few conferences. As I got lot of requirement to explain it in more details, I’ll write about good example of BC integrations with one other Dynamics 365 solution – with ‘Dynamics 365 Talent’.

‘Dynamics 365 Talent’ is a new Microsoft Dynamics HCM solution (new name ‘Dynamics 365 Human Resources‘). This solution was initially based on AX HRM, but now it is separated solution. As we can use it independently and this solution is really amazing HCM system, I think it can be interesting how we can integrate this solution with Business Central and make them as the powerful tool together… and with no code.

If you are thinking how to make it and how to make it with no code, the answer is using one of the Azure services – Logic Apps. As ‘Dynamics 365 Talent’ has entities on CDS and Logic Apps has connectors for CDS and for ‘Business Central’, only what we need to do is to map entities and fields in both systems and of course, to think abut business logic on the first place. Depends what is the primary reason for integration, we can choose some of the options:

  • integrate HRM core system with HR in Business Central
  • integrate Attract or Onboard apps in Talent with Business Central.

In second option, we will use HR module in Business Central and use only one or two parts from ‘Dynamics 365 Talent’. On the other side, in first option we will use core HR in ‘Dynamics 365 Talent’. In this text, I chose to explain the first option.

In this first text, I’ll just explain some basic concepts and you will find more details in the following texts with this topic.

Basic setup in Business Central

First, as we don’t need all HR capabilities in Business Central (we already have all of them in dedicated HR solution – ‘Dynamics 365 Talent’), we will move only data necessary for other areas in Business Central. In this example I’ll show how to move data to Employee table as this table can be used for example in a Payroll system or you can use this information in Fixed Assets card.

Locate information in Talent

Now when we have the basic configurations, we can continue with integration. First, we need to find where an employee’s data are saved in Talent. To find this we need to open list of CDS entities and we can do it using PowerApps platform.

When we have these basic information, we can continue with technical parts how to do it in a practice.

Dynamics 365 Business Central Updated Roadmap

A few days ago, after the first day and first keynote of Directions NA, I’ve posted Business Central roadmap. But now after this event has finished, we can find updated roadmap for our NAV successor – Dynamics 365 Business Central and it looks very interesting:

D365BC Roadmap

I’ll wait Directions EMEA to collect all information and write more detailed about this, but from my point of few, big changes are coming in two years and this is the last moment to change some old habits and to continue our journey in modern business applications.

Licensing in Dynamics 365 for Talent

In a last period, I’ve got a lot of questions about how to make a proper licensing for Dynamics 365 for Talent. As it is a new solution, it is understandable. As I’ve already wrote a few articles about this product, I think I can help with some answers.

The first and very important, all users in this solution are named users. And if we speak about HR core part, we have two different user types and you can buy them on two separate ways. We have Full Users with total access to all HR core application and we have Team Members with very limited access (mostly, but not only for read tasks).

As I mentioned Full Users (Talent Users) can be bought on the following ways:

  • as a regular Talent User (you must take minimum 5 users) for 40 USD
  • buying Dynamics 365 for Finance and Operations, i.e. you will get full Talent Users buying Unified Operation (for 190 USD) or full Dynamics 365 Plan (for 210 USD); in both cases you will get much much more than just Talent, but Talent will be part of your completely system.

TalentLicense.PNG

If we are speaking about Team Members, you can buy them for 8 USD, but again you will not get only access to Talent with them, but also to all other Apps in Dynamics 365 package. As I mentioned, Team Member are not limited only with read rights, because you can use them for example as employee for Employee Self Service.

OK, but this is not the end. Recently, Microsoft announce two additional AI Apps for Talent (Attract and Onboard) and that means if you want to use them, you first must be a regular Talent User. Then, you can subscribe them. Price is 8 USD for each of them separately or if you want both, price will be 12 USD in total.

And again, this is not the end. Actually, it doesn’t mean it must be the end. Why? Because if you want to customize something. As you already know (I hope), this App is full SaaS and you cannot just open a code and change it. If you want to change something on forms and similar, you can do it using PowerApps. In this case person who will make these customizations must have PowerApps Plan 2 (40 USD) license, but other users who will use these forms, have to have minimum PowerApps Plan 1 (7 USD) license. That means, not all users, only these who will use these new features. And just to know, if you are buying some Dynamics Plan, you will get PowerApps for free.

PowerAppsLicense.PNG

And again, it is similar situation if you want to use PowerBI for additional reports or Flow for additional workflows.

I hope I covered all models of licensing here. But just keep in mind, it is possible to be some changed, because it is a new App in Dynamics 365 family and with new releases, it is possible to be some changes. And I didn’t mentioned, but just to be sure: all pries are on monthly basis.

My Session(s) on eXtreme 365 Conference

This year I’ll start with my sessions little bit earlier then usually. My first conference where I’ll have a lecture will be eXtreme in Dubrovnik. In a past, this conference was mainly for the Dynamics CRM solutions, but from the 2017., we have not only CRM, but AX, NAV… as well.

So, this year I’ll be there with minimum one session. I’ll speak about Dynamics 365 ‘Tenerife’ (and NAV as well) in a real world of integrations using Flow and CDS. I hope it will be interesting. If I’ll have more lectures, I’ll announce it here as well.

In a mean time, you can go and check more details about eXtreme 365 conference here, and I recommend to register if this is suitable for you.

eXtreme365.PNG

Dynamics NAV and Microsoft Flow

Hi, for all of you who want to learn how to use Dynamics NAV and Dynamics 365 for Financials with Microsoft Flow in a practice, I’ll provide webinar together with NAVUG.

navug

Today I just want to share this information with you and I’ll keep you in touch. Soon more on NAVUG web site. For now, just to save a date, it will be at Wednesday, February 14, 2018 (9:00AM-10:00AM EST).

All sessions from NAV TechDays 2017

NAV TechDays 2017 has just finished a few days ago and I already wrote about my expressions. Now, all sessions are already published and I want to have all of them on the one place. There are all of them:

Opening Keynote

Deep dive into the new development tools by Stanislaw Stempin, Jesper Schulz-Wedde and Esben Nyhuus Kristoffersen (all from Microsoft Development Center Copenhagen)

Desktop & Mobile Client Enhancements by Horina Serbanescu, Andrea Tino and Tomas Grubliauskas (all from Microsoft Development Center Copenhagen)

Application SaaSification by Henrik Frovst Madsen and Tommaso Pimpo (all from Microsoft Development Center Copenhagen)

Azure Functions Deep Dive by Vjeko Babic (Cloud Ready Software)

C/AL, Coding for Performance by Jasminka Thunes (NxM Business Solutions) and Jörg Stryk (STRYK System Improvement)

Creating great API’s by Anders Larsen and Nikola Kukrika (all from Microsoft Development Center Copenhagen)

Rock ‘n Roll with VSCode by Waldo (iFacto & Cloud Ready Software)

PowerApps, Common Data Services and Common Data Model by Michael Nielsen (ForNAV) and Mark Brummel (NAV Skills)

Easier and DevOps-friendly Dynamics NAV environments using Docker / Windows Containers by Tobias Fenster (Axians Infoma), Jakub Vaňák (Marques Olivia) and Freddy Kristiansen (MDCC)

Best practices to get automated tests running on your solution by Luc van Vugt (fluxxus.nl) and James Crowter (Technology Management)

Office 365 business apps powered by Dynamics 365 “Tenerife” platform by Ievgenii Korovin, Andreas Moth and Monica Ahuja (all from Microsoft Development Center Copenhagen)

Source Code Management with Visual Studio Code Made Easy by Soren Klemmensen (360 Visibility) and Jonas Andersen (Elbek & Vejrup)

Enjoy and see you there the next year…

The future of NAV – a small wrap up

These days we got a lot of messages about the future of our product – Dynamics NAV. Now I’m seating in a plane and traveling to Nashville on NAVUG Summit and finally have found some time to make a small wrap up with all important things. I think now, after two Directions in North America and EMEA, picture is clearer.

Roadmap

The first thing I want to mention is roadmap of Dynamics NAV. I think it is absolutely clear that in this moment we have Dynamics NAV 2017 as ‘on prem’ and ‘on cloud ready’ solution, but as SaaS, we have Dynamics 365 for Financial and Operations Business Edition, generally based on Dynamics NAV. But this is just in this moment, because Marko Perisic announced in Madrid last week that we will have published Dynamics NAV 2018 at December 1st. This announced is mostly based on partners feedback and this is absolutely this what partners wanted. For now, SaaS solution will stay the same, with the same name and in the same countries (US, Canada and UK). But with this new NAV version, partners will get new solution and the most important, with this new NAV version they can start to use Visual Studio Code for Extensions v2. This is important because partners now can start immediately with new model of development and to be ready for the spring and new solution.

NAV##1

At the spring 2018, we will finally get already announced new product – Dynamics 365 “Tenerife”, but only as cloud SaaS solution. As on-prem solution, we will get Dynamics NAV 2018 R2, but with the same code base as Dynamics 365 “Tenerife”. In this moment I don’t know a reason why we will still have the same product with the different names ‘on cloud’ and ‘on prem’. But very soon, we will continue with only one name – currently code name Dynamics 365 ‘Tenerife’. System will have new modern web interface, sandbox and lot of new features (more about it in another post).

And ant the spring, we will get Dynamics 365 for Sales App with less features (ex Business Edition) and Dynamics 365 for Marketing as preview. Both of these products was presented on Directions and they really look nice and rich.

New Package – New Opportunities

As I said, I don’t want to write about all new features in the future release, but what with the whole package. The main idea is to stop to implement ERP and/or CRM; but to continue to implement full business solution. This is what clients need; they don’t care what part of system it is, the just need to solve their problems and their requirements. And as the new business solution, we will have Dynamics 365 as business solution who cover most of the potential client’s needs. That means we will not sell e.g. ERP, but solution. In this solution we will see what real requirements client has and implement adequate Apps with adequate level of features. Price will depend of this, but we will don’t know prices, because of lot of changes. By my opinion, very important is that now we can combine Apps from ex Business Edition and ex Enterprise Edition. With this we will have more agility in implementation process. And of course, all of this will be integrated with Common Data Service. And even better, we can use CDS for our integrations. We can use not only Dynamics 365 Apps, but also PowerApps, Flow, Office 365, Power BI, 3th party Apps… as the same business environment.

NAV##2

Conclusion

The final message is by my opinion very clear and very positive. For both partners and customers. Don’t afraid, Microsoft will not stop with this amazing product. Rebranding is not canceling. But with new name, we will get still the same powerful product, but with the great new opportunities as well.

I can write probably more, but I think this is more than enough as the first wrap up after two Directions. Future of our product is a clear.