Creating complex JSON structure in AL and Business Central

preview_player
Показать описание

Рекомендации по теме
Комментарии
Автор

Very helpful, Sir! I watched all json videos, and more videos regarding other topics. Your content is making a big difference. Thank you!

sufletdemustang
Автор

Keep up the good work Erik

Little workaroud for pretty json

local procedure PrettyJson(var JsonText: Text)
var
JSONManagement: Codeunit "JSON Management";
begin
if then begin
JsonText :=
end;
end;

brianjuhl
Автор

Nice one Erik, just wonder have you ever met json with special characters. Like when exporting Item Card in Description you have special charcaters like " or tab or ' or *
I've read we can use like \" or so but that means have to search all char in the description.

stefanushendra
Автор

Great as always, Erik!

A question.
Is it all of them really called "Keys" and not "JSON Tokens"?
I know for instance when you make an API to Sales Invoice, for example, BC will return a token called "Key" with a JSON Value.

Much oblige

jonaslundstrom
Автор

Kan du lave en video om hvordan man laver en page i bc hvor man kan sende en ticket til zendesk. Jeg har hul igennem Zendesk api'et via postman, og jeg har en side klar lavet i AL, men jeg kan ikke lige gennemskue hvordan jeg poster til api'et i AL

youneselhamss
Автор

How do you store an array of values for one fiield ? e.g. "Field1" : "["Value1", "Value2", "Value3"]

realeques
Автор

VSCode does know how to format json. Paste it into a .json file and do ‘format document’. No need for external dev toys

drimmelzwaan
Автор

Thanks for the valuable content Erik! Perhaps you could get into making such complex structures available thru an API?
We as BC Developers are constantly confronted with interfaces from and to external systems. But, MS has only the API Page for us to publish a REST/JSON API. The problem there is, you can only go 2 levels deep with a subpage. Yes there’s a OdataEDMType but 1. you cannot place an array (edm collection type) into another OdataEDMType and 2. it is deprecated since version 6, leaving us with an API Page and Subpage, max 2 levels deep. Since 3 versions no replacement for it! This is a joke. I wish they would allow a JSONObject Parameter in a codeunit, that way you could publish that codeunit as a web service and the parameter passes the json object, respectively XMLDocument. What’s your point of view? Perhaps i am missing something? Thanks Erik!

sakis
Автор

Great Erik

A question.

Could you please make a tutorial about differences between adding header to an http client with DefaultRequestHeaders and with and HttpHeaders.Add.

Thank you ever so much