From the Microsoft Dynamics 365 Business Central blogs: Table fields; Project success; Dimensions; Compliance

In this week’s review of Dynamics 365 Business Central blogs: 

• Why not start supporting the JSON data type for table fields?
• Unlock project success with BC and Project Operations
• Dimensions in Business Central
• Simplifies compliance for hassle-free audits

Why not start supporting the JSON data type for table fields?

On his blog, Stefano Demiliani wrote that recently he has worked on cloud applications using Azure SQL as the backend, with extensive use of JSON documents. 

He stated that this experience has made him consider an old idea: adding support for the JSON data type in table fields within Microsoft Dynamics 365 Business Central.

Demiliani noted that Azure SQL Database has supported the JSON data type for over a year, allowing storage of JSON documents in a binary format that improves storage efficiency and query speed. He then explained the advantages of this new data type. He wrote that:

The JSON type internally stores data using UTF-8 encoding, Latin1_General_100_BIN2_UTF8 and this behavior matches the JSON specification.

Demiliani added that Azure SQL also supports a set of aggregates and operators designed for efficient handling of JSON documents that make working with JSON data fast and effective. He then offered some examples of how to create a table with a JSON field.

Unlock project success with Dynamics 365 Business Central and Project Operations

FREE Membership Required to View Full Content:

Joining MSDynamicsWorld.com gives you free, unlimited access to news, analysis, white papers, case studies, product brochures, and more. You can also receive periodic email newsletters with the latest relevant articles and content updates.
Learn more about us here

Get full access

or login