T
|
Tim 10/7/2019 |
Hi Pete, |
jadachDevClub member 10/7/2019 | |
Hi Pete, I also use AD and dynamic permissions and was getting this error in 10.3. I worked with support last week and figured this out and it requires 2 things. First, make sure your "ugrights" table has the new "Page" field. ASPR should add this field automatically when you open an old project in 10.3 (make sure you have the latest build, just released), but in my case it didn't work because the user I connect to the DB with didn't have the rights to add this field, so I had to add it manually. The data type is "text". Second, I had to go to the securities page, switch the table used by dynamic permission to new ones and let ASPR create them (again, user needs permissions). Then build the project once, and then I can go back to the securities page and switch it back to the original tables and it seems to work. This second step might still point to a bug, but at least it's a workaround. I just had a thought; maybe if I synced the DB after manually adding the new "Page" field I wouldn't have to do this second step. I'll test that. Good luck, Tim
|
Pete K author 10/7/2019 | |
Thanks, Tim! I always start out using integrated Windows authentication when building a new app, then once all tables are generated, I switch to a SQL account with only datareader and datawriter roles. So I guess that step was failing for me also. I think they should add a warning when that happens, as they currently do when trying to add other tables. Probably just an oversight. |
admin 10/7/2019 | |
Installing the latest build and re-building the project should take care of this issue. If this doesn't help then what Tim said, adding a new TEXT field named Page to _ugrights table and synchronizing project and database will take care of this. |