11
Views
2
Comments
Solved
[Service Studio] - Compilation Error

Hi OS comunity,

Me and a co-worker of mine are having an issue when publishing a traditional web app. We are getting the following error message:

Internal Error

Compilation Error.

referencesProxy\Extension_TABLE1_proxy.cs(34,40): error CS0234: The type or namespace name 'ENTABLE1Entity' does not exist in the namespace 'OutSystems.NssTABLES_DB' (are you missing an assembly reference?) return OutSystems.NssTABLES_DB.ENTABLE1Entity.ViewName(tenant, locale);

State: Build References Proxy


I have used TABLE1 and TABLES_DB as example, in order to not use the real names.
What do we think may be causing the problem:

-We had an extension with many tables, what was not ideal practise. So we created some more extensions and distributed the entities in those. We did not delete any extension to do this. We only migrated some Entities from an extension to others;

-We did some clones of the main extension with the most entities, and in each clone we deleted the entities we didn't need for those new smaller extensions with fewer entities;
-Only two entities are triggering this error message, one of them we changed the name in integration studio;


So, this was running smoothly, we had been working on the app for some time, published the modules 20 times or so after that, no problem. Someday, we started having this compilation errors. Here is what we have tried so far:

- Refreshing all the modules references and publishing them;
- Removing the entities causing the errors from the modules and publishing (works, but we those entities :D), and when we add the entities again, it triggers the error again;

-Republishing the extension in the integration studio;

-Deleting the extension with the entities that cause the problem, creating a new one, and using it;

-Creating another UI module similar to the one we were using the entities on.

-In the BL layer module it also triggers the same error, but in the CS base layer module of the UI one it works fine. We updated the references of all modules and republished them. 

-We even checked the extension .NET source code to see if in the defined namespace something was missing, but we didn't notice any flaws. 


Finally, nothing seems to fix the issue, we don't know what to do anymore, besides starting a new app from scratch, but because of two entities causing the issue, it is a lot of work!


Thank you for your time if you read until now, hopefully you can help with this one,

best regards,

André Almeida.



2025-11-12 11-25-02
André Almeida
Solution

Thanks for the reply. That was not the problem. Fortunately, we tried one more thing and it solved the issue. I added the entities to an extension that we were already using with another name, removed all the dependencies from every module for the broken extension and added the references we needed from the extension we already had created. Finally we deleted the broken extension. 

Uff, problem solved, took us all day but we got it :)

Hope this helps someone in the future,

Take care!

UserImage.jpg
Nino Gachechiladze

By the chance,Is there any warning in this compilation error module?  which tells that there is some undefined object or something similar?

if it is, you should check and see, sometimes there is non-mandatory variables  do not display an error if the type they are using like Record, or list of record of structure or entity is deleted and it causes compilation error.

I don't know if it is the case, but hope it helps

2025-11-12 11-25-02
André Almeida
Solution

Thanks for the reply. That was not the problem. Fortunately, we tried one more thing and it solved the issue. I added the entities to an extension that we were already using with another name, removed all the dependencies from every module for the broken extension and added the references we needed from the extension we already had created. Finally we deleted the broken extension. 

Uff, problem solved, took us all day but we got it :)

Hope this helps someone in the future,

Take care!

Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.