Refresher ignores view

Posts   
 
    
Torsten
User
Posts: 26
Joined: 13-Mar-2015
# Posted on: 12-Feb-2020 13:45:18   

After I migrate our project from 4.2 to 5.6.1 successfully (thx for your help again), I am facing a new problem:

I added a new view to our mssql db so I start to sync the Relational Model Data.

In the "Perform Tasks..." gui, the new view is listed und I checked it for generation. But after the sync there is no entity/entry for this.

It isn't thery neither with gui nor with CliSyncWithDatabase. And also, there is no error message or something similar for that element.

Am I doing something wrong. In 4.2 we used only the CLIRefresher and everything works fine if we add a table or view.

BTW: Is there any chance to get the source code for CliSyncWithDatabase? In v4.2 we had made some extensions we would like to have in 5.6.

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39588
Joined: 17-Aug-2003
# Posted on: 12-Feb-2020 17:11:29   

Is the view visible in the catalog explorer after the sync? If so, you can reverse engineer it using the normal tools in the designer (right-click schemas or the catalog and select reverse engineer views to entities... or typed views, what you prefer).

It's not done automatically because likely the setting 'Add new views as entities after relational model data sync' is not checked in the project settings. Project settings -> Entity Model -> Database first Development, check 'Add new views as entities after relational model data sync', click ok and after that when you add a new view to the database it should then automatically be added as an entity after the sync.

We don't have plans to open source the clisync tool at this time, but perhaps we can adjust it a bit for the extensions you want to add? Could you elaborate a bit which extensions that might be?

Frans Bouma | Lead developer LLBLGen Pro
Torsten
User
Posts: 26
Joined: 13-Mar-2015
# Posted on: 17-Feb-2020 09:08:29   

Thanks for that hint. I checked the settings you mentioned and the refresh is working.

I am now facing another problem. But it occurs while runtime, so I open a new thread!