This is the 3rd blog of this series, before this I have created a blog on the first topic “Perform initial configuration steps” from Module 1 which you can check here : MB2-877 Microsoft...(read more)![]()
MB2-877 Microsoft Dynamics 365 for Field Service Module 1 Topic – Configure product and service pricing
↧
↧
PowerApps integration with Microsoft Dynamics 365 Business Central Online
PowerApps integration with Microsoft Dynamics 365 Business Central Online
#1 – POWERAPPS
What is PowerApps?
“PowerApps” is a Cloud Based and “No Code” solution offered by Office 365 platform to create web based and mobile-data-connected apps”
PowerApps is a suite of apps, services, connectors and data platform that provides a rapid application development environment to build custom apps for your business needs. Using PowerApps, you can quickly build custom business apps that connect to your business data stored either in the underlying data platform (Common Data Service for Apps) or in various online and on-premises data sources (SharePoint, Excel, Office 365, Dynamics 365, SQL Server, and so on).
The “NO CODE” Philosophy is the “DOGMA” and the base of PowerApps, using PowerApps, you can create two types of apps: Canvas and model-driven.
To create an app, you start with web.powerapps.com
- PowerApps Studio is the app designer used for building canvas apps. The app designer makes creating apps feel more like building a slide deck in Microsoft PowerPoint. More information: Generate an app from data
- App designer for model-driven apps lets you define the sitemap and add components to build a model-driven app. More information: Design model-driven apps using app designer
What is a connector?
- Enables communication between PowerApps and any publicly exposed set of APIs
- Anyone using PowerApps can use any of the available connectors
- PowerApps can act as a middle tier to enable communication between unrelated services
- Each connector offers a set of operations classified as ‘Actions’ and ‘Triggers’
Link https://docs.microsoft.com/en-us/powerapps/powerapps-overview
#2 – BUILDING A NEW POWERAPP
4 Steps to Build a new PowerApp
#3 – SHARING YOUR APP
#4 – POWERAPP DEMO FOR DYNAMICS 365 BUSINESS CENTRAL
PowerApps Login https://powerapps.microsoft.com/en-us/
Admin Page https://admin.powerapps.com/home
CREATE YOUR NEW MANUAL CUSTOM APP
- Create a NEW App
- Set an app name for saving in your local or cloud repository
CONFIGURE YOUR APP (COLOR, LAYOUT, STYLE, TYPE)
“SAVE AS” YOUR APP (in Local or in Cloud)
DEFINE A DATA CONNECTION – EXAMPLE FOR BUSINESS CENTRAL SAAS CONNECTOR
SELECT DATA SOURCE (FROM EXISTING CONNECTION)
- In this case from “CRONUS.IT” (DEMO DATABASE)
- Data Sources (Web Services Odata must be existing and defined previously)
DATA TABLE from DATA CONNECTIONS
… NOW YOU CAN BUILD AND CUSTOMIZE YOUR NEWAPP
APP WIZARD TEST: CONNECT TO “CUSTOMER ODATA” FROM APP WIZARD
- TO CREATE A NEW APP: SELECT CONNECTION > SELECT CUSTOMER TABLE (ODATA EXPOSED)
- WIZARD GENERATE A NEW APP… WAIT FOR COMPLETITION
- Is a Silent Wizard based on exposed Web services structure
EXAMPLE with “Customer” table object exposed as native connection, system triggers: Add Insert, Delete, Modify + Refresh button are available on Builded App.
Table “Customer” , Direct exposure
Page workflowCustomer a Web Services (Odata), Manual Exposure
… AND WAIT FOR COMPLETITION…
YOUR APP IS READY!
- CUSTOMER APP IS GENERATED AND READY TO USE, YOU CAN PERSONALIZE YOUR APP
C – MODIFY AND CUSTOMIZE YOUR APP
EXAMPLE: MODIFY\ADD NEW FIELDS
EXAMPLE: INSERT A “BUTTON” WITH CONDITIONS
BUTTON ON FORM WITH CONDITIONS (IF..THEN)
D- TEST YOUR APP: INSERT A NEW CUSTOMER OR DELETE A CUSTOMER
#5 – SOME NICE LINKS TO BUILD YOUR APPS!
Get started with PowerApps
https://powerapps.microsoft.com/en-us/tutorials/getting-started/
https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/powerapps-custom-visual
Building a Custom Connectors
Nice Link from NAV Team Blog https://blogs.msdn.microsoft.com/nav/2018/07/05/create-apps-with-powerapps-and-dynamics-nav/
↧
Job to apply vendor prepayment on (PO) invoice through X++ code in D365
Prepayments are a common business practice, with organizations issuing prepayments to vendors for goods or services before those goods or services are fulfilled. To minimize risk, you can track prepayments...(read more)![]()
↧
MB2-877 Microsoft Dynamics 365 for Field Service Module 1 Topic – Configure bookable resources
This is the 4th blog of this series, before this I have created a blog on the topic “configure products andservices pricing” from Module 1 which you can check here : MB2-877 MICROSOFT DYNAMICS...(read more)![]()
↧
Tips&Tricks: Assembly Management Scenarios
A series of Tips&Trick will be located in a Tips&Tricks page on the blog to be dedicated to publish every quarter of the year the last tips and tricks that illustrate a specific function on Microsoft...(read more)![]()
↧
↧
Inventory value adjustments (Part 1)
In this post, I show you how you can make use of electronic reporting and MS Flow to create automatic inventory value adjustments in MSDyn365FO based on the inventory turn / inventory days of items. The...(read more)![]()
↧
NAVTECHDAYS #THEBEST
Luck Van Dyck did it ... once again. #NAVTechDays 2018 where the best I've ever seen!
Content
NAVTechDays were always special because of the content. All other conferences are focusing on management...(read more)![]()
↧
Using Azure Bot Service to create Bot
Using Microsoft Bot Framework Azure Bot Service is an integrated environment that allow us to easily register, build, deploy our bots. It provides the required components and hosting environment for creating...(read more)![]()
↧
MB2-877 MICROSOFT DYNAMICS 365 FOR FIELD SERVICE MODULE 1 TOPIC – Configure additional options
This is the 5th blog of this series, before this I have created a blog on the topic “Configure bookable resources” from Module 1 which you can check here : MB2-877 MICROSOFT DYNAMICS 365 FOR FIELD SERVICE...(read more)![]()
↧
↧
Attaching files to a record through Canvas Apps, using the Common Data Service Connector
I found this very cool little piece of functionality that allows you to attach a document directly to a record within a canvas app by leveraging standard functionality within the Common Data Service (CDS...(read more)![]()
↧
Job to get the print management report format name through X++ code in D365
Recently I have a got a requirement in which I want to get the SSRS report format name selected in print management settings, for that I have created a job to get the report format name in print management...(read more)![]()
↧
MB2-877 MICROSOFT DYNAMICS 365 FOR FIELD SERVICE MODULE 1 TOPIC – Integrate other tools with Field Service
This is the 6th blog of this series, before this I have created a blog on the topic “Configure additional options” from Module 1 which you can check here : MB2-877 MICROSOFT DYNAMICS 365 FOR FIELD...(read more)![]()
↧
Consumir una API REST en Dynamics 365 for Finance and Operations usando RestSharp
En uno de nuestros últimos proyectos implantando #MSDyn365FO nos ha surgido la necesidad de consumir un API REST para realizar una serie de integraciones entre el ERP y aplicaciones externas. En esta...(read more)![]()
↧
↧
Tips 会社幹部をお客様の幹部の方へ紹介する際に
初めてのBlog投稿となりますので、簡単に自己紹介をさせていただきます。日本マイクロソフト株式会社にてプリセールス エンジニアのマネージメントを行っております御代（ミヨ）と申します。
以前もこのBlogではありませんが、お客様から伺った業務の実利用のアイディアや製品のTipsなどを共有しておりましたが、この度こちらのBlogにも参画させていただくことになりました。
お客様とお話をさせていただいている際に時々話に出てくる...(read more)![]()
↧
How to handle a new TAG in the ISO20022 bank statements - Dynamics 365 for Finance & Operations
Hi All,
In Microsoft Dynamics 365 for Finance and Operations, against the Advanced bank reconciliation Module, we can import electronic bank statements and automatically reconcile them.
The article below will explain the set up processes for reconciliation.
Advanced bank reconciliation setup process
Days ago I spent some time in order to handle a new XML Tag.
The link below explain the basic setup. The Bank Statement import varies, depending on the format of your electronic bank statement. F&O supports three bank statement formats out of the box: ISO20022, MT940, and BAI2.
Set up the advanced bank reconciliation import process
So, for instance if you have to handle a new Column/Tag into the Bank Statement Lines table (BankStmtISOReportEntry), you have to:
In Microsoft Dynamics 365 for Finance and Operations, against the Advanced bank reconciliation Module, we can import electronic bank statements and automatically reconcile them.
The article below will explain the set up processes for reconciliation.
Advanced bank reconciliation setup process
Days ago I spent some time in order to handle a new XML Tag.
The link below explain the basic setup. The Bank Statement import varies, depending on the format of your electronic bank statement. F&O supports three bank statement formats out of the box: ISO20022, MT940, and BAI2.
Set up the advanced bank reconciliation import process
So, for instance if you have to handle a new Column/Tag into the Bank Statement Lines table (BankStmtISOReportEntry), you have to:
- Add the new field to the BankStmtISOReportEntry table
- Add the same field to the BankStatementLineStaging table and BankStatementLineEntity Data Entity
- Edit the SampleBankCompositeEntity.xml file and Add the new Tag according the new Field added to the Step 1
- Edit the BankReconiliation-to-Composite.xslt trasformation file and add the new Tag. In my case I searched for another "similar" tag for the same Entity and I replicate all found entries and change the name
- Edit the ISO20022XML-to-Reconciliation.xslt trasformation file, found the entry and Add the new Tag Section. Also in that case I have copied another "similar" section and change the name
- Lastly, in F&O recreate the Entity in the Data Management Processing Group
- Test the file Import
Take a look also to the link below in order to, for instance, Debug an XSLT file.
That's it!
↧
Considerations when "upgrading" Dyn365FO from 8.0 to 8.1
Version 8.0 of Microsoft Dynamics 365 for Finance and Operations was released summer 2018. Just a few months later, in October, version 8.1 was released. If you have environments running version 8.0, let it be development environments, demo environments, or even production and (tier 2+) sandboxes, you might be thinking about getting them "upgraded" to 8.1. It's not really an upgrade, but actually rather an update.
The overall process is actually a lot easier compared from coming from 7.x. I did a series of posts on how to get started here:
https://yetanotherdynamicsaxblog.blogspot.com/2018/11/upgrade-from-7x-to-8-series-post-1.html
Microsoft outlines the process in one single article here:
https://docs.microsoft.com/en-us/dynamics365/unified-operations/dev-itpro/migration-upgrade/appupdate-80-81
![]()
So in effect, when servicing 8.1+ you get only one update tile, and it contains everything, and you download everything cumulative. You'll use the complete update package to patch your environments, and there is no need to put the updates in VSTS either. Things are just so much easier.
But you do not need to compile Microsofts packages, so who cares if the code is wrong? Well, what if you want to debug, extend, view code? Even though you do not need to recompile Microsofts packages, you run the risk of having invalid, incomplete or even erroneous code on your development environment. So it just follows your best option is to redeploy a new set of development boxes and of course build box(es), and depending on your choice of server size and storage, the deploy of new servers they might be ready for you within 3-4 hours.
But before you connect the newly deployed development environments to the source code, it is paramount that you prepare a new 8.1 branch, which is clean from updates. It may contain 8.0 extension modules, but not any Microsoft modules. You can prepare all of this while the new environments are being deployed.
![]()
Well, unfortunately it might not just be that simple. If the environment has other non-Microsoft packages installed, LCS will prevent you from simply apply the update package. You may have some ISV-solutions or some package you've created and released, and then installed on the environment, through LCS.
LCS knows about this, and can list the non-Microsoft packages installed. In fact, if you try apply the update package, LCS will stop you, and list the packages blocking you.
![]()
Error: "Modules on the environment do not match with modules in the package. Missing modules: [...]"
In order to continue, you will need to get a pre-compiled version of these modules where they were built on a 8.1 environment. Depending on your scenario, that either means getting the 8.1 version from a vendor or partner, or simply just get your package built and released through your new and shiny 8.1 boxes.
As it is stated in the upgrade guide, you are recommended to prepare yourself one single build release of all the extension modules and packages. When you have the 8.1 package ready in the Asset Library, you can simply merge it with the update package, and execute the update.
![]()
If all your demo and test environments where using the same set of non-Microsoft packages and modules, you'll simply reuse the same merged package to update all of them.
Happy updating!
![]()
The overall process is actually a lot easier compared from coming from 7.x. I did a series of posts on how to get started here:
https://yetanotherdynamicsaxblog.blogspot.com/2018/11/upgrade-from-7x-to-8-series-post-1.html
Microsoft outlines the process in one single article here:
https://docs.microsoft.com/en-us/dynamics365/unified-operations/dev-itpro/migration-upgrade/appupdate-80-81
Why update?
One of the main differences between 8.0 and 8.1 is the latter version is a lot easier to service with updates. Version 8.0 still supports individual application hotfixes, meaning you will download and apply them, put them in VSTS, just as you would with 7.x. You could argue the possibility to pick individual hotfixes and avoid taking all updates is a good thing, but in fact it is not the way forward. Instead of thinking that you may have to avoid hotfixes, and potentially have to "roll back" updates that breaks you, you need to shift to a mindset where any ongoing issues are immediately reported back to Microsoft which allows them to ship new updates that resolves any issues, not only for you, but for us all. With that mindset, you will want to take the 8.1 version, which does not allow for individual hotfixes, but instead gives you everything cumulative at the point you pick updates. This is also how "One Version" will behave, and on April 2019 you will be getting updates in this fashion.
So in effect, when servicing 8.1+ you get only one update tile, and it contains everything, and you download everything cumulative. You'll use the complete update package to patch your environments, and there is no need to put the updates in VSTS either. Things are just so much easier.
Development and build environments
Even though Microsoft has a Software Deployable Package that does the update from 8.0 to 8.1 in the Shared Asset library in LCS, it is recommended that you deploy new 8.1 build and development environments. Why is that, you may ask. For a development environment, you will have both source code and a runtime (code compiled). Your 8.0 development environment might even have been updated with hotfixes, added back in time. Part of the process is to remove any 8.0 updates, and start from scratch with 8.1. So when you start removing already committed Microsoft application updates form Azure DevOps (VSTS), you cannot avoid this to also reflect your local copy of the source code.But you do not need to compile Microsofts packages, so who cares if the code is wrong? Well, what if you want to debug, extend, view code? Even though you do not need to recompile Microsofts packages, you run the risk of having invalid, incomplete or even erroneous code on your development environment. So it just follows your best option is to redeploy a new set of development boxes and of course build box(es), and depending on your choice of server size and storage, the deploy of new servers they might be ready for you within 3-4 hours.
But before you connect the newly deployed development environments to the source code, it is paramount that you prepare a new 8.1 branch, which is clean from updates. It may contain 8.0 extension modules, but not any Microsoft modules. You can prepare all of this while the new environments are being deployed.
Non-development environments
What about demo, test and sandboxes? Well, typically you do not care about the source code on the demo boxes (even though it might be there), and as for acceptance test sandboxes, where you do not even have Visual Studio, it definitely doesn't matter. These environments you could just go ahead and update using the Software Deployable Package.
Well, unfortunately it might not just be that simple. If the environment has other non-Microsoft packages installed, LCS will prevent you from simply apply the update package. You may have some ISV-solutions or some package you've created and released, and then installed on the environment, through LCS.
LCS knows about this, and can list the non-Microsoft packages installed. In fact, if you try apply the update package, LCS will stop you, and list the packages blocking you.
Error: "Modules on the environment do not match with modules in the package. Missing modules: [...]"
In order to continue, you will need to get a pre-compiled version of these modules where they were built on a 8.1 environment. Depending on your scenario, that either means getting the 8.1 version from a vendor or partner, or simply just get your package built and released through your new and shiny 8.1 boxes.
As it is stated in the upgrade guide, you are recommended to prepare yourself one single build release of all the extension modules and packages. When you have the 8.1 package ready in the Asset Library, you can simply merge it with the update package, and execute the update.
If all your demo and test environments where using the same set of non-Microsoft packages and modules, you'll simply reuse the same merged package to update all of them.
Happy updating!
↧
Dynamics 365 Project Service Automation: Pricing Dimensions – Part I
Tested on:
Dynamics 365 version 9.2, PSA solution version 3.2, Unified Interface
Pricing and the whole financial aspect to project management has always played a huge part in Dynamics 365 Project Service Automation. Before Pricing Dimensions (also know as Multidimensional Pricing or MDP) was released in PSA version 3 as part of the Spring ’18 release, the only OOTB dimensions for pricing were Role and Organizational Unit. This article series will shed some light on Pricing Dimensions, however...(read more)![]()
↧
↧
Apply Payable Document Error
↧
6 Key Benefits of Cloud Computing for SMBs in 2018
Cloud computing is more than just a trending topic or industry buzzword. It’s a game-changing approach to managing data that has already proven its staying power and its impact on businesses’ productivity, profit margins, and growth potential. The benefits of cloud computing are numerous, but they’re particularly impactful for small and mid-sized businesses (SMBs).
But before we dive into these advantages, let’s take a step back to understand what cloud computing is, and what its impact has looked like thus far.
What is Cloud Computing (and Why is Everyone Talking About It)?
To put it simply, cloud computing is an approach to hosting and maintaining data via — as you can probably guess — the cloud.
Some examples of cloud services (or delivery models) may sound more familiar than the more general term; they include Software as a Service (SaaS), Infrastructure as a Service (IaaS), and Platform as A Service (PaaS). You’ve probably heard those terms come up quite frequently as of late. It seems that cloud computing is top-of-mind for organizations of all sizes these days.
And there’s a reason for it.
Unlike it’s on-premise counterpart (in which data is hosted via dedicated, in-house servers), cloud computing offers a more scalable approach by hosting, managing, and processing data in the cloud. This means organizations can stop worrying about managing systems and data in-house, thus freeing up time to focus on bigger priorities, like cost-savings, scalability, and revenue growth.
How Cloud Computing Has Proven Its Staying Power
Cloud computing has been around for quite some time, and we’ve been seeing just how well it pays off since as early as 2013.
In fact, over four years ago, nearly one-quarter of businesses investing in cloud computing were already seeing improvements in time to market, increases in efficiency, and reductions in operational and IT costs. In 2015, Dell reported that companies investing in cloud solutions were seeing nearly 50% faster revenue growth than their competitors.
These benefits of cloud computing are even more commonplace today, and we’re seeing an even longer list of advantages becoming the norm.
Why Both Large Enterprises and SMBs are Investing in Cloud Computing
By 2020, it’s predicted that the cloud computing market will be worth $162 billion, seeing an average year-over-year growth rate of 19%.
Across industries, businesses recognize the considerable revenue opportunity, and many are already trying to claim a piece of the pie:
- 73% of large enterprises have invested in cloud solutions.
- This number is expected to jump to 90% by 2019.
For SMBs, adoption is slower, but gaining traction.
- Sixty-two percent have already adopted cloud solutions.
- Another 33% plan to do so in the near future.
Businesses of all sizes have high hopes for cloud solutions, but larger organizations have a slightly different focus and objective than smaller ones.
This year, 76% of large enterprises prioritized improving the speed of IT delivery as the most important outcome of investing in a cloud solution, while only 66% of SMBs did. For bigger organizations, this priority item was closely followed by a focus on achieving more flexibility to adapt to a changing marketplace. For SMBs, the highest priority that followed was enabling business stability, growth, and scalability.
With small businesses focused more heavily than larger ones on enabling growth, there is potential for exponential progress in the short-term. Larger organizations, on the other hand, are more focused on improving existing processes and preparing for the future, making it less likely that they will see the same marked improvements in business growth today.
SMBs are seeing the benefits of cloud computing pay off in a big way. Here are some of the advantages we’re already seeing, and others we’re expecting to see moving forward:
The Benefits of Cloud Computing for SMBs So Far (and On the Horizon)
In 2018, 81% of companies say that operating in cloud computing has had at least a moderate (and often outstanding) effect on their automation efforts. Over 40% of businesses who have adopted cloud solutions wish they had done so sooner. But for SMBs, the results of investing in cloud computing are even more impressive. They can include:
1. Lower Costs
In addition to a reduction in hardware costs, a cloud solution allows SMBs to take advantage of a pay-as-you-go subscription model, and eliminates the large up-front cost of an on-premise solution.
2. Better Efficiency and Productivity
Implementation is faster, cloud-hosted information is more easily shared, and your IT team’s time is freed up without the need to manage or maintain your cloud infrastructure.
3. Faster Speed to Implementation (With Cloud ERPs)
As early as 2014, businesses with SaaS or cloud ERPs were reaching their first go-live milestone 19% faster than those with on-premise ERP solutions. This speed has remained a benefit of SaaS ERPs today.
4. Increased Security
Data is backed up off-site, reducing the risk of cyber security attacks and mitigating the challenges of recovering data during a potential outage.
5. Eliminating Manual Software Updates
There’s no software update installation needed; your software will always be updated in real-time to the latest available version.
6. Scalability
Thanks to cloud solutions’ ability to change alongside your business needs, you will have increased flexibility to grow and scale with minimal hiccups or hurdles. Plus, as your business grows, you won’t need to pay for additional hardware or worry about more maintenance.
And these benefits aren’t just hypothetical.
Many SMBs have already begun to see the benefits of cloud computing (or have been for years already). Many SMBs who have invested in cloud solutions have seen:
- Profits double
- Including an additional 25% revenue growth
- A 400% increase in productivity
- More agility in business operations (for 74% of SMBs)
- Reduced IT and operating costs
- And the ability to reinvest cost-savings into their business
- Improved security (for 94% of SMBs)
Is your organization an SMB considering an investment in cloud solutions?
Even if you’re already running Microsoft Dynamics 365 Business Central or SAP S/4 HANA, you should know: your ERP isn’t the only aspect of your business strategy that can benefit from being hosted in the cloud. You can reap the benefits of cloud computing with a SaaS e-commerce approach (integrated with a cloud ERP, or an on-premise ERP). That’s where Sana comes in.
Curious about how Sana’s SaaS solution can play a role in strengthening your e-commerce strategy? Learn more about the benefits of SaaS from our recent blog or download our fact sheet for more insight on Sana SaaS.
↧
Actuals vs Estimated hours myth
All these years I was calculating Actuals as the billable hours on the project with chargeable role.
While PSA helped me cleared the myth. Below is how PSA helped me clear that myth and this is how I...(read more)![]()
↧
