Tag Counting Journal in Dynamics 365 for Finance and Operations
D365UG Summit | What’s New in Financials and UI
Microsoft presented today at D365UG summit on some of the new UI, Financials, and Production features available.
Presenters: Jason Green, Mike Faulkner, Philippe Jacobsen
Check the Release notes for the specific estimated release date of these features. Some may be released in early 2019 or beyond.
Web Client
I covered some of the enhancements to the web client released in Platform 20 in a previous post.
What’s Coming
Collapsible navigation in menus will simplify finding a menu item.
New options will be available for saved views on forms, which allows for multiple personalizations on a form.
New grid capabilities will include:
- Improved scrolling – more data will be held client side so the scroll is more accurate and not paginated
- Filter/sort on any column including “display fields”
- Excel-style column filtering – pick filters from list
- Grand totals on grids
- Grouping and subtotaling on grids
- Cross-column search
- Remove 10,000 record Download to Excel limit – not infinite, probably 1 million records
Finance
I’ll be doing an upcoming live AXUG webinar on October 31st called “What’s New in the D365 for Finance and Operations Fall 2018 Release (8.1, Platform 20)” that will cover many of the new features discussed during the session and will include live demos.
Revenue Recognition
The Revenue Recognition features are used when billing is done at a summary Sales Order level, but the Revenue needs to be split out. New capabilities will be added to allow for this split.
Enterprise Credit Management
Ability to put orders on hold and have global credit limits.
Supply Chain
All kinds of Performance improvements.
How do I see my TODO comments?
Blockchain for EDI: How Secure is it?
Data Masons is pleased to present our blog series on Blockchain and EDI. Blockchain is quickly becoming less of a buzzword and more of an inevitability in the B2B world as more companies utilize it in their business practices, including in EDI processes. We're starting our series by addressing the most important question that accompanies any new technology. How secure is it? Sometimes it seems like technological advances face a constant battle between ease of use and security.
While no technology can be completely risk-free, Blockchain does have some advantages due to the way information is added and stored, and security protocols which are unique to Blockchain. Read on to learn more about how security works, and what it means for you as an EDI user.
What, Exactly, is on that Chain?
Whenever a transaction is processed using Blockchain (also known as “the Block), it is added to a limitless chain of linked transactions, or blocks. This distributes a copy of the chain and transaction throughout the Blockchain network, which results in a decentralized, distributed ledger.
The Security of Immutability
The blocks in the chain are immutable, which means that they can’t be modified once they’re added. If changes need to be made, this requires a separate correcting transaction, rather than a change to the transaction itself.
Even though shifting from correcting ledgers to creating new ledgers for corrections could be a pain, it has a couple of advantages. First, it will force companies to adjust their business practices to minimize the chance of mistakes and the need for corrective transactions. Second, it makes it extremely difficult for the data to be attacked because of security protocols such as Proof of Work.
Smart Contracts to the Rescue
But the need for corrections will be minimized, thanks to Smart Contracts. We'll cover them more in depth in a future blog post, but simply put, Smart Contracts will do the work to make sure that each transaction is correct BEFORE it takes place, without the need for human intervention. Today’s method often relies on validation from disparate and disconnected systems, but a Smart Contract provides another type of security for Blockchain users: assurance that transactions are correct before and after they take place.
We'll also go over immutability in the future, including, why exactly a block is unchangeable, but here’s what it means in terms of security: if a hacker or other malicious party wants to alter any data on the Block, it would mean altering the entire chain, and they would not be able to achieve a consensus. The definition of consensus in terms of a Blockchain principle is outlined in further detail in Blockgeek’s awesome post, but suffice it to say, it’s a necessity of any Blockchain transaction, and makes Blockchain a much more secure way of doing business than today’s standards.
Is Your EDI System Ready?
The bottom line, though, is that the Block is only as secure as the software interacting with it. It’s an exciting buzzword and you want to make sure that your EDI system is not only eager to use it, but prepared to keep it secure and give you the peace of mind that you need. Download our brief or read the upcoming posts in our Blockchain and EDI series to learn more about how to evaluate your EDI system for this emerging innovation.
PUG Summit | Understanding Time Intelligence with Power BI
Presenter: Dan Edwards
Auto Date Fields
Power BI can create automatic date hierarchies, for report and drill down by Year/Quarter/Month/Day. It’s important to consider whether your data model has more than one fact table with a date attribute. If there are multiple facts, or you have already created a date table, it’s a better to use your own date dimension.
“Don’t use auto date/time” -Dan
I love these types of tips and tricks – here’s how it works, and don’t do it!
Creating a Date Table with DAX
It’s possible to use a DAX expression to create a date table. The initial DAX expression looks like this:
Date = CALENDAR(“1/1/2016”, “12/31/2019”)
Use the DAX expression to create a New table in Power BI.
Then additional columns can be added to the Date dimension table:
Month = MONTH(‘DATE'[Date])
It’s also possible to do concepts like MonthDate where you calculate a Date column with the first day of every month, which can provide flexibility.
MonthDate = DATE( YEAR(‘DATE'[Date]) , MONTH(‘DATE'[Date]) , 1 )
Using an Effective Date
One of the scenarios is a scenario where the user wants to pick the effective date – for example a cutoff date or the last 12 months.
Dan mentioned he has a fairly extensive blog post on how to implement this concept.
Great presentation!