Closed jimmymcp closed 2 years ago
Can you provide a set of sample projects that reproduce the issue and a video of the unexpected behavior?
I've just tried a simple repro and it works as expected. I will harder to break it later, for now this is a snip of my code and the compiler output.
The Type field is a "Sales Line Type" field and the table belongs to the PROD app. The compiler error is in the TEST app.
Actually, looks like there is something more fundamental here. Hopefully you can see in this gif that my field shows in intellisense but fails to build. Not sure how to get more info about what is going on here? This field is supplied by a table extension in the PROD app. I'm attempting to reference in and build the dependent TEST app.
Update: I had been disabling code analysis in the TEST app. Enabling that (CodeCop, UICop) solves the problem 🤔
I saw something far related when my project references were not correctly defined, or when they weren't loaded yet.
Could you try the following?
Hi! In the last months, we've been working hard on adding new features that increase your productivity and on improving the quality of the tools. Unfortunately, this meant that we were not able to follow up on as many GitHub issues as we would have liked.
If this is still a problem in the latest insiders build, feel free to raise this issue again.
I have an app (call it PROD) with a table of type enum which uses a the Sales Line Type enum from the base app. I also have a test app (call it TEST) which is dependent upon the first.
I can see my enum field in intellisense when working in TEST but the compiler throws an error saying that the definition of the field cannot be found. For now I have had to workaround using SetFieldValue from the Data Type Management codeunit.
I have the same behaviour with a table extension in PROD adding a field to a standard table of type enum with an enum that is defined in PROD. Again, when developing in TEST I can write the code to assign the field value but the compiler throws an error. Again, using SetFieldValue is a workaround for now.
AL Language v6.1.359074