I updated to 1.6.5 beta. Apparently there are some changes to the security tables and I need to propagate those changes to my security dbs. Except I forgot how to do this. I know how to update changes that I make in the DDT, but I forgot how to make changes when they start in the db. So, I assume I need to some how update the DDT profile with the new changes, then after that I can figure it out.



Thanks!

Hey Greg!

Not sure this is the solution you are looking for, but for the us_displayname that has been created, I've been re-building the Security source code to solve the problem by now.

I'm not following you Ivan. What do you mean you're rebuilding the security source code?

Greg,

Attached is the updated security.pkg file that has all of the updates structures.  Copy this to the C:\Program Files\Common Files\MicroFour\StrataFrame folder.  You can then re-import this into your profile...or manually add the changed fields....I recommend the first option

Ivan was just saying that he manually added the us_DisplayName field to his structures and moved on with life...but you can take this PKG file and the go into the DDT and click the Profile -> Add Security Tables and it should update your security structures in your profile...but as always, make a copy or backup of your existing PKG file first so you can restore it if necessary...but you shouldn't have any issues.

OK, its coming back to me. Just had a bit of a brain fart there for a minute (or ten). Thanks for the package!

I guess that after a while trying to understand "what this Brazilian is saying now?!", Trent developed a way to automaticaly translate everyting into his brains real-time.

LOL. Most of the time I understand just fine, Ivan (well, except when you are typing in Portuguese).



OK, I'm having a problem deploying the new security stuff. I updated the security tables with the new package you sent Trent. That seemed to go fine. I'm not sure what else has changed, but there is now a us_displayname field in the SFSUsers table.



However, when I go to create the package, I get an exception (see attachment).



Any ideas? This is causing some grief as I can't test any security features...

When and how are you getting this error message?

OK, Greg. Let's see if you really understand me...

Regarding the exception, would you like trying to delete your Security Data Deployment package from the DDT and adding them back again?

Almost as soon as I click on the create package button.