NAV18 VSCode: Referencing customized objects in object designer

maze93

Hi all and thanks for a great site.
Up until now I have found an answer to all of my questions during the years just by searching for them here. Unfortunately, this is not the case for this question.

I have set up an NAV 2018 database with VSCode and AL language (the vsix from the installation package, not the market place since this seems to be missing some features). In this case I have a third party product which I need to install outside VSCode as a FOB in object designer. The objects do not touch any standard objects. However, what I was expecting was that when I update the symbols in VSCode, these objects should present themselves before me.

(FYI: Local database, not in the cloud!)

This is not what is happening...
Does anyone know if there is anyway of referencing I.E. a codeunit in VSCode to a codeunit in object designer (object id greater or equal to 50 000)?
I am not very keen on upgrading the third party solution to an extension since there is 70-80 objects in there.
And yes, I have used the txt2al-converter, but this only gets me so far with lots of other trouble when trying to compile tables, pages etc. since they all rely on each other. Therefore this is not what I would like to do.

Thank you very much!
Regards from Mattias

logger

Hi @maze93 ,
Have you already tried to regenerate symbols as described here - https://docs.microsoft.com/en-us/dynamics-nav/developer/devenv-running-cside-and-al-side-by-side ?

logger

@maze93 , you are welcome.

logger

Hi @maze93 ,
Have you already tried to regenerate symbols as described here - https://docs.microsoft.com/en-us/dynamics-nav/developer/devenv-running-cside-and-al-side-by-side ?

maze93

Hi @logger and thanks for your response.

I hadn't tried that but did now. Unfortunately no difference.
I can see in the object meta table that the table is generated:


I have run the code for regenerating and then also tried to restart the instance.
I have both these options set as true:


However, it still will not recognize the codeunit from VSCode.


Also: I redownloaded the symbols in VSCode again.

Any other suggestions? :-)

Thanks!

maze93

Hi again @logger

You are a life saver. It seems you are indeed correct.
However, the first part did not work for me:


But the second part did:


I have no clue why but after I ran the second exemple it actually worked.
Amazing, I was getting so frustrated about this.

Thank you again!

Regards from Mattias

logger

@maze93 , you are welcome.