Thanks!

rss.app/feed/UOnw76Z...

vld-bc.com/rss.xml

And one last thought, this application is intended for administrators. Only those with Data Editor permissions can use it, or those with SUPER permissions. Only for right people.

However, if you’re granting SUPER or Data Editor(!) permissions to every user, you might be doing something wrong :)

I worked and sometimes work with old versions and yes in those versions you can for example delete entries or modify them.

"not changed since 20 years"
this is for sure not about Business Central

btw I add important block to article and general page again, so everyone can read about risks once more )

Or maybe it’s just a bug in the compiler or the programming language interpreter, lol. 😄

Software is no exception, we can never be completely certain about it. Even if our code is written perfectly, who knows, maybe a high-energy cosmic particle is already on its way to break everything? ieeexplore.ieee.org/document/212...

We live in a subjective world of uncertainty where there are no guarantees anywhere. Even our perception of the physical world is entirely subjective. Can you say for sure that I see the color yellow the same way you do?

You have to believe in people!

A lot of people are aware of this :)

In any case, I have feedback that many people have found this app very useful, especially consultants. And the responsibility for use lies entirely with whoever use it, as specified in MIT license. I just repeatedly warned about careful use -)

That's what Microsoft thinks, too. Meanwhile, a lot of people are suffering. I can understand restrictions on Production, but on sandbox it's already very strange. Same with OnPrem.
You can find there not only G/L Entry -)

Of course! Switch isn't going anywhere anyway, let everyone choose how they prefer )

Wow, I didn't know anyone else was using rss. I'll see what I can do about that :)

@phenno.bsky.social Got it, fixed it! Thanks for your vigilance!

I think books of this kind need visualizations, it's hard to imagine if this can be perceived in audio format -)

It is convenient when we do not know in advance what files will be in the future, for example, a new client with new files for import/export.

But supporting these mapping (data), supporting code around them with different complex cases (e.g. nesting depth), it is not easy at all.

I wrote and maintain such functionality that flexibly customizes mapping in data. And for many XML/JSON/CSV/EXCEL formats. It is convenient when we need to parse different files by structure, in this case you can just change the data, not the code.

Writing a functionality where you will store all these mapping nuances in the data is not worth it. As it is not such a simple story as it may seem at first glance.