Thank you, Erik. I needed this but it will take some time for me to "digest" what you explain here.

This really saved my butt, thank you!!

@Hougaard

Жыл бұрын

That's what we do here :)

For this to be the "ONLY procedure you need", I'm missing that it's able to create new dimension values on the fly if they don't exist for that specific dimension code.

@Hougaard

3 ай бұрын

I think there's a video on that somewhere on the channel :)

BTW, the rename error you were getting is a known error that MS has in their bug list. A workaround is it to put a line break (new line) just before the VAR and do the rename. This only seems to happen with VAR parameters and I normally see it in functions with a long parameter list where the end of the line is not visible in the in the code window (or very close to it). Natalie Karolak(sp?) had a Tweet about this a few months ago.

@natiidrb6622

Жыл бұрын

I started working with BC about 3 years ago and I remember it being there all along! :D I always have to use that line break hack you mentioned, but I wonder what's taking them so long to fix it..?

@nemanjavelickovic9062

3 ай бұрын

@@natiidrb6622 I guess it is taking them too long to fix it is because it terminates reading the line if it encounters " ;/n " but in this there is no "/n" so it thinks the starting apostrophe and the closing apostrophe refer to the same string, but in reality they are two parameters, and I guess the RegEx for that one is maybe hard to come with, because you can have many parameters in one function. Soo new line is basically the easy-fix that everyone can come up with, so it will stay :)

You know whats fun. When one of the dim set id's is broken. So the ID doesnt match your selection anymore.

Hi Eric, We recently moved to BC 22 on Prem. We are noticing a weird issue. In Purchase Line and FA GL journal , we have to enter short cut dimension ( 2, 3,4,5,6,7,8) before shortcut dimension 1 . If we enter Shortcut dim 1 before other shortcut dimensions, somehow it does not recognize shortcut 1 dimension. It says that the shortcut dimension 1 is missing. Do we have any solution for this? I am not sure what we are doing wrong. It is so strange. It works in the Sandbox but not in the production. We don't have any issue with Shortcut dimension 2 (Which is Global Dimension 2). The order we enter has become critical now. We get an error ‘The Property code (shortcut dimension 1) is missing in line 10000. We have entered the value. When we reenter it again, it recognizes the value.

Hi Erik, out of Dim topic, but can you also make a video how to create custom approval workflow on BC? Happy New year!🥳

@Hougaard

2 жыл бұрын

It's just a long a tedious process, would make for a boring video I'm afraid... See here: docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-walkthrough-workflow-events-responses

Hi, can this be used for Dimension Corrections? Is it possible to just change the dimension set id on G/L Entry with the revised set? Grate videos btw.

@Hougaard

Жыл бұрын

But that already exists?

Hii, erik thankyou for giving me the knowledge about default dimension flows in standard but i want to do in our custom table then how can i do pls make a videos on custom table for flowing the default dimension same as sales order or give me any tips to do it or refer any link thankyou.....

I think the Rec.Modify() is not needed because you use this is a var in the UpdateDimSetOnSalesHeader which already modifies it?

New BC developer here! Love your videos, do you have one discussing Install and Upgrade codeunits?

@Hougaard

2 жыл бұрын

Not yet, soo much stuf to cover :)

Assuming Rec.modify(true) pops the update lines confirmation message to pass it down to the line level too?

@Hougaard

2 жыл бұрын

No, that's validating the dimension set id field doing that.

Tak er kun et fattigt ord 🙂

F