Today I would like to briefly talk about how to export all keys in all tables.
In AL, a key definition is a sequence of one or more field IDs from a table. You can define keys in table objects and table extension objects, depending on the type of key. There are two types of keys: primary and secondary.
Business Central allows us to perform Isolated Storage, which is extremely useful if, for example, we want to store Passwords, Tokes, and Secrets without having to resort to Tables.
A couple of weeks ago I made a post on How to Test Outh2, through the native Business Central codeunit, but every time we closed the window, the token disappeared. So I came up with a good example idea, adding Isolate Storage to mitigate this issue.
Business Central, being a “kid” from the 80’ties, rocks classic alphanumeric primary keys. In this video, I take a look at the primary key situation, check it out:
Today I would like to talk about an interesting method in Business Central customization, how to get fields in the keys of the table.
As you might know, in AL, a key definition is a sequence of one or more field IDs from a table. You can define keys in table objects and table extension objects, depending on the type of key. There are two types of keys: primary and secondary.
In this video, I explore the new feature in Microsoft Dynamics 365 Business Central v18 where it’s possible to add keys on base fields.
Azure Key Vault is a cloud service for securely storing and accessing secrets. A secret is anything that you want to tightly control access to, such as license keys, credentials, API keys, certificates and so on.
Starting form Dynamics 365 Business Central 2020 Wave 2 (version 17) you can start using Azure Key Vault service for storing your secrets and then retrieving them from AL code in a very easy way.
One of the most common errors you’ll see when working with Power Query in Power BI or Excel is this:
Expression.Error: The key didn’t match any rows in the table