Hi Erik, I am watching this video from India. It have been working On AL for last 6 months. When I started your videos were flowing over my head. Now I found your videos pretty useful. Keep it up.

Interesting to see what would happen if you use in the code "Database::Customer" and you have 2 "Customer" tables in different namespaces :)

@aidanharper3784

7 ай бұрын

Perhaps there'll be an update where if namespaces are used you'll have to fully qualify Database::TableName like Database::Hougaard.Demos.Namespace.Customer?

@cl10

7 ай бұрын

The Customer name should be fully qualifiable

I hit a use-case for namespaces just today, as a client of ours has a Currency extension in app A, and our additional app B which depends on app A *also* has a Currency extension. Luckily it's a simple matter of a name change and extensions don't require a ForceSync (as the SQL table is called {appId}.Currency) but a namespace would be neater.

tks a lot

Microsoft should start approving top level name spaces asap. Don't wait 6 months 🙂

Hi Erik thanks for the video. Do we need to implement it? or is it optional?

@Hougaard

7 ай бұрын

You well need to do it at some point...

I don't know why but with the last update, the AL language extension is very slow.

Question 1) I have been using prefixes in my object names. With namespaces, can I assume that the prefix is no longer needed? Making the code more readable. Question 2: Do you think object numbers will be discontinued? I don't see the need for them when using namespaces. Or am I missing something? Question 3: What about having a project namespace? So that we don't have to specify it for each object.

@finnpedersen9342

5 ай бұрын

Thanks for a great video on the subject. Especially your take on how to use NestedNamespace. I did not find any best practices from Microsoft. I am implementing namespaces in all my projects.

@Hougaard

5 ай бұрын

Microsoft still require affixes for AppSource apps...

@Hougaard

5 ай бұрын

Object Numbers are not going away, that will be too expensive for the whole channel... There's too many places where the object numbers are also data.

Why not use our prefix as the top namespace?

@Hougaard

7 ай бұрын

It will become visible to endusers, so make it more readable :)