We are pleased to announce the re-release of KB3163813 with title “CU12 Known Issue – Incorrect Posting amounts – Shipment Packing slip posting”.

KB3163813 was originally shipped in September 2016, with title “SO processing performance issue”. It was released as a separate hotfix and also included in Microsoft Dynamics AX2012 R3 CU12. The original hotfix can, in the scenarios mentioned below, cause incorrect amounts to be posted in the general ledger, when processing a Sales order packing slip posting. These incorrect postings will cause reconciliation discrepancies between the inventory subledger and general ledger.

Below are the known scenarios where the issue is likely to occur.

Known scenarios

1. WMSII scenario:

• The released product is associated with an item model group where Post physical inventory to ledger = True or Post to Deferred Revenue Account on sales delivery = True, and
• Sales order line lot ID is split based on output orders and grouped in the same shipment, and
• Sales packing slip is posted from Inventory management>Common>Shipments.

1. Warehouse Management (WHS) scenario:

• The released product is a warehouse (WHS) management enabled item, and
• The released product is associated with an item model group where Post physical inventory to ledger = True or Post to Deferred Revenue Account on sales delivery = True, and
• Sales order line lot ID is split based on loads, and
• Sales packing slip is posted from any of the forms under path Warehouse management>Common>Shipments>.

If the original KB has been deployed and one of the two scenarios has occurred, the voucher associated with the sales order packing slip posting is likely to result in overstated monetary amounts. As a result, the general ledger most likely will not reconcile against the inventory subledger. The inventory subledger will however have the correct physical monetary amount.

Exceptions

Below are the 2 exceptions where the voucher associated with the sales order packing slip posting will have correct monetary amounts, when the original KB has been deployed and one of the two scenarios has occurred.

1. If the original KB3163813 has been deployed and the sales line has either a project association or the legal entity is Russia (RU), then the voucher associated with the sales order packing slip posting will have the correct monetary amounts.
2. If the original KB3163813 has been deployed and sales order packing slip is posted from the sales order form or from the Sales and marketing>Periodic>Sales update>Packing Slip, then the voucher associated with the sales order packing slip posting will also have correct monetary amounts.

Re-released KB

This issue has been fixed and KB3163813 has been re-released with the updated title “CU12 Known Issue – Incorrect Posting amounts – Shipment Packing slip posting”. Customers who deployed the original KB3163813 “SO processing performance issue” are advised to deploy the re-released KB (KB3163813“CU12 Known Issue – Incorrect Posting amounts – Shipment Packing slip posting”).

This re-released KB is available for Microsoft Dynamics AX 2012 R3.

Application stores are a mainstay of every modern operating system. Microsoft is working towards bringing this concept to the business application space.

The Dynamics 365 App Source concept allows ISVs and partners to bring their addons to a centralized marketplace. App Source can help partners and customers find business users and customers. On the flip side, customers can find validated solutions that have gone through a validation and approval process.

Unlike a traditional App Store, business apps are generally more complex to implement than a PC or mobile app. Many times code, business processes, and data need to be tested and promoted to various systems to make the solution work. The Dynamics 365 for Operations App Source site connects to a management toolkit called Lifecycle Services that helps strategically deploy the key assets into various environments.

At the tech conference, Shefy Manayil Kareem (@Shefymk) from Microsoft discussed the following key features of App Source:

• A new publishing portal for Dynamics 365 due later in 2017
• For ISVs, improved actionable insights for App Source hits and leads
• New predictable trial experience
• Announcement of “Test Drive”, where a managed environment is already running and ISVs can temporarily allow access to an environment for a prospective customer
• Leveraging multiple components from D365 Operations, Sales, PSA, PowerBI, Common Data Service, and Power Apps
• Reviews and ratings displayed in App Source based on the trial experience

The App Source concept is a few years old, and continues to round into form. Key upcoming features like Test Drive should lead to simpler trial experiences should significantly increase the value of having a solution on App Source. Ultimately, ISVs and partners hope to decrease the time for prospects to investigate the features of an product and drive sales.

The Common Data Service (CDS) has been a much discussed concept since the middle of 2016 when Dynamics 365 was first announced. The way this feature is described sometimes seems like CDS is the unicorn of the Dynamics 365 world – it solves any problem.

Sometimes what gets lost in this story is the basics – CDS is a new, simplified database concept. The advantage of the new CDS approach is a faster setup, deployment, and management of the data model, user interfaces, and integrations.

Environments

Environments group features together in CDS including:

• A collection of tables and table relationships – aka creating a database
• Publishing Power Apps aka a user interface
• Integration and mapping tools connected to Dynamics 365

Common Data Model

The CDM is the definition of tables and table relationships. The Microsoft published CDM is geared towards the Dynamics 365 entities and used for integrating multiple D365 products. 

Power Apps

In many of the CDS demos Microsoft shows Power Apps with CDS, which sometimes conflates the technology. The database components of CDS don’t require a Power App to be used. 

Power Apps are most…powerful when they combine requirements from multiple systems into a single experience. For example, there may be multiple systems that do issue or task management, and each system may require its own fields. A Power App can be created with all the fields required across all systems, then the integration features to push issues into each system will work swimmingly.

Integrations

CDS entities eventually will be used to pass data back and forth between Dynamics 365 databases. There’s a focus by Microsoft to provide some scenario based integrations for things like Order to Cash scenarios between Dynamics 365 Sales and Operations. 

There are a couple of mechanisms for passing data back and forth. Microsoft Flow is most commonly used in demos because it supports many products, but there’s also a more “native” integration feature that will pass data more efficiently for Dynamics 365. The integration features also include data transformation logic.

Templates 

Templates are used to deploy the CDM, PowerApps, and Flows/Integrations as an Environment. 

Admin Center

The Admin Center is a portal for designing, publishing, and maintaining the CDS environment. 

This portal also manages the security. They key components of security like table level and record level security are in the toolkit.

Summary

There is a lot of interesting technology around the CDS. But right now it seems like the CDS is a solution in search of a problem. There needs to be simple examples of the technology solving specific problems for Dynamics 365 for Operations customers to jump in on this new feature set.

Microsoft will probably hate the comparison , but I think of CDS in the same way as people used to use Access databases. Access databases were simple, limited, specific tools; many times they were disposable as technology evolved. Conceptually CDS may be an evolution of that story. If the business use case is longer term, it may be better to build features and UIs directly in a Dynamics 365 product.

D365 for Operations needs a simpler way to define and export groups of entities from a source environment, and transform and import data into a target environment. 

Microsoft is building some brand new (and long needed) tools for importing and exporting configurations between companies, environments, and default/template data environments. Mike Falkner led the session demoing the new features.

Define and Export

The Data Management UI is getting a refresh to be more usable in a number of areas:

• Better overall organization of Workspace
• Lists instead of tiles
• Easier picking of entities into a group, including mass picking
• Manual and automatic sequencing improvements

Transform and Import

There weren’t demoable features ready on this side of the equation. The general approach is supposed to be hard coded rules that can transform specific entities. The import should be simplified by more quickly selecting and importing multiple Data Packages.

Summary

I’m very happy to see more features in this area. The current features are workable, but every step takes longer than ideal. Look for features to come out this spring, with a quick and iterative release cadence.

• Purpose Built
• Productive
• Intelligent
• Adaptable

• Change
• Quality of Data
• Training
• Business process change

• Immersive experience
• Continuous update
• Effective change management, Data Governance, Complete solutions

• Single instance based in US East
• 7 Global distribution centres
• 5000 Employees
• 6 ISV Solutions
• Entire project implementation in a span of 15 months
• Intercompany processes
• 15000 order lines via EDI
• 550 users live
• No terminal services, direct connection

• Over 100 entities
• Consolidation
• Increased awareness of costs
• Reduction in reporting cycle timeframes
• Tracking invoices from receipt to payment
• 6 months Development time
• Partner - Empired

• Intelligence Insights
• Productive experiences
• Continuous life
• Business anytime, anywhere

• Hybrid / On-Premises
• Around June 2017 timeframe,  local support to run in your own datacenter
• Upgrade framework AX 2012 R3
• Extensibility - How to keep customers current and using extensions
• Extensions to configure and customize the applications
• Power BI Content Pack  - drill through into details
• In the spring release, 10 Power BI Dashboards to be released
• Customer Ageing Report in mobile device
• Expense Management Mobile Demo
• Offline capability
• Power BI Content Pack Credit collections
• Preview version of AX 2009 Upgrade

• Ability to customers having visibility to their product life cycle(Design , marketing, seel, manufacturing, distribute, service)
• Brings the data together from disparate data sources - bring data into one common area
• Product Graph - the name of the project for bringing common data services together
• Product Explorer - can take data from different data sources like SAP, CRM, and put together and relate it
• Product Explorer - Filter by Product Attributes
• Preview in late spring 2017

• Cloud, Cloud + Edge, Local Business Data
• Microsoft recommends Cloud as the preferred medium of deployment
• In June, local business data option would be available - disconnected from cloud, Run in your own data center, scenarios where internet connectivity is problem, data sovereignty issue, enterprises who are yet to buy into the concept of cloud.We will not have Power BI, Embedded analytics, machine learning capabilites, product graph, will not be available for on-premise local deployment option
• Deployment for all 3 options is through LCS
• The 3rd deployment option is hybrid - combine power of cloud + immense potential of data centers, Federated instances, each manufacturing instance can run , syncrhronizing data into cloud, no other erp provides this
• Demo on cloud + edge
• The synch happens in the background, Demo to create a sales order in edge and it comes into cloud (master) - Preview in Spring

I snapped this photo of a slide shown during the keynote. Great information!

Cloud

Cloud + edge

Local business data

However I’m currently extremely busy on several projects and also preparing some speaker sessions for a local Dynamics community and also the Summit EMEA 2017, I would like to share a solution to solve an authentication error when using the Microsoft Office Add-in. You will probably not face this issue when you are using machines in your own domain.

The problem

Using my own laptop accessing a test environment of a customer I wanted to Open the customers in Excel. In Dynamics 365 for Operations you can click the Office button to Export data or Open data in Excel. What is the difference between Export and Open here? Well, Export will create an Excel file with static data where Open will create an Excel file with embedded Office add-on to be able to refresh and also publish data back to Dynamics 365.

During login an Authentication error occurs for me when accessing this customer sandbox environment from my work laptop.

Looking at some error details the next error is raised:

AADSTS50058: A silent sign-in request was sent but no user is signed in. The cookies used to represent the user’s session were not sent in the request to Azure AD. This can happen if the user is using Internet Explorer or Edge, and the web app sending the silent sign-in request is in different IE security zone than the Azure AD endpoint (login.microsoftonline.com). Trace ID: ae185b5c-b397-4b49-b3d1-790e1c9a67aa Correlation ID: 04007e36-a31d-4968-92c5-3fe70bfa5f59

In simple words: My laptop is not part of the domain of the customer. When trying to login, you will then continuously notice the attempts fails. Again and again and again…

The solution

When you click the User menu, you will get a menu with the option to Sign out.

When you sign out, the next form will then be presented. Usually you will close a browser, but in this case, the login page is embedded in the Excel add-on. The User menu is not visible and at first sight, there is no option to continue. So we are a bit confused now…

When you click the form space a small menu icon will be presented which can  be used to open a Microsoft Dynamics menu. Then click Reload. You can also right click on the white space to get a pop-up menu with the option for reloading the page. The step to really sign out can be avoided. If you are able to open the Microsoft Dynamics menu, you just have to Reload the page to get rid of the silent sign-in attempt.

When the page is reloaded, you can sign-in with the required login credentials.

When you have provided the correct credentials, you can continue using the Excel add-on.

That’s all for now. Till next time!

Microsoft Dynamics AX CommunitySubscribe to this blogger RSS FeedMy book on Merging global address book records in AX 2012 [/custom_button

The post How to solve Microsoft Office Add-in authentication error in Dynamics 365 for Operations appeared first on Kaya Consulting.

The March release for Dynamics AX 2012 R3 version is now available in LCS on the updates tile inside your R3 project. This update represents a typical collection of smaller functional improvements and technical fixes.  Bugs were fixed in all areas with enhancements found in Warehouse Management, Procurement and Cash Management. Please see the full list of hotfixes below to search for your specific issue newly included in this release. This release is a cumulative package including all other fixes released in the prior CU12 update.

Here are a few details related to this release:

·        Primary Build: 6.3.5000.3124

·        Number of Application hotfixes: 116

·        Number of Binary hotfixes: 14

Details of the install process can be found here: https://technet.microsoft.com/en-us/library/hh538446.aspx#PackageR3

What is included in this month’s release?

Design Change Requests, Feature Requests & RegFs

Fixes Released

User types

Pricing

Slide from D365 Tech conference showing Dynamics 365 pricing

The information we received about pricing as it relates to cloud + edge and local business data deployments.

Support

The most complex slide I have seen this week...

Discounts

Discounts are good - Limited time offer!

Last year I blogged about Workspaces in Dynamics 365 as a concept. At this year’s Tech Conference, TJ Vasser talked about some of the newly available features on the reporting side. TJ highlighted his own blog post about the various reporting options available for Dynamics 365 for Operations.

Analytical Workspaces

Up until March 2017, the only option for bringing Power BI content into D365O was to publish content packs in PowerBI.com, and each user had to link a Workspace to that published content pack. With Platform Update 4, it’s now possible to embed Power BI content packs directly into a Workspace. Embedding Power BI into Workspaces should remove much of the effort from the end user, and shifts the work to reporting analysts and developers.

The major components of the embedded experience are:

• Adding a new form, or adding a Workspace tab.
• Defining the .pbix files that are embedded in the Workspace.
• Writing a controller class that links the .pbix file to the form, manages filters and security, and defines drill-through experiences.

It’s Not All Rainbows

There are many caveats to this story – when investigating D365O and Power BI features, it’s always a good idea to prototype the entire process before building out any specific feature. Some of the caveats for the embedded reports include:

• Currently only Entity store is supported; using your own database (BYODB) is unsupported.
• Embedded Power BI requires a developer and code promotion; publishing to PowerBI.com is easier to make fast changes.
• It is possible to drill through from the embedded report, but each drill-through experiences require an Event handler in code.
• There are better options for dynamic filtering experiences, but these also require development.

 Summary

Simplifying the user experience and bringing reporting into the app will make embedded Power BI a powerful tool. I anticipate quite a bit of development effort to provide awesome experiences. I also suspect the change management process for embedded could be problematic. It’s a good step in the right direction and is worth exploring. 

The below table lists the current updates released for Microsoft Dynamics AX 2012 R3.

Please see the notes column for more information about each cumulative update.

*Expiration dates for Microsoft Dynamics AX 2012 R3 are found here.

Getting Started

Analyze

Data clean up

SQL configuration

Deprecated features

Pre-upgrade checklist

Execute

ISVs

Work toward a successful compile

Start at the bottom and work your way up

Development tips

Data upgrade process

Script process

Errors

Validate

Smoke test examples

• All servers started
• All server components accessible
• Review that expected data is there
• General ledger reconciles to 2012
• Inventory reconciles to 2012

Conclusion

We know that one of the biggest challenges for many companies using Microsoft Dynamics AX is Reporting. 

It can be difficult to understand AX Reporting structures and whether or not third-party integrations are needed to accomplish your Reporting needs. For answers to these questions and more join your peers at our AXUG Focus conference, held May 8-9, 2017 in St. Louis, MO, for in-person training delivered by Industry Experts.

AXUG Focus grew from the desire of Dynamics users to dig deeper into the topics most pertinent for success in their role/industry. Attendees can customize their learning plan based on their needs and network with peers in similar roles who face the same issues on a daily basis. The knowledge gained can be used to train others within attendees’ organizations.

Here is a preview of some of the sessions that cover Reporting topics:

• Managing Information towards One Source for Reporting, Analytics & Business Intelligence
• Get the Most out of Management Reporter - Great features that are often overlooked
• Diving Into Financial Reporting with Management Reporter

Click here to browse the full AXUG Focus agenda, comprised of 90-minute, deep-dive sessions concentrating on four specific tracks: Finance, Retail, Supply Chain Management, and Technical.

Let the Dynamics AX User Group (AXUG) community solve your challenges and save your sanity. Don't forget to register before the Early Bird pricing deadline on March 22!

Want access to Power BI Deep-Dive Sessions?

Power BI helps organize data visually to create dashboards, spot trends & produce interactive reports. To learn more about this powerful tool, register for PBIUG Focus, held May 10-11 at the same location as AXUG Focus.

Originally posted on axug.com