...
[16:23:57 CDT(-0500)] <dmccallum54> it has already been removed from the importable entities, so wont be added to new installs
[16:31:48 CDT(-0500)] <jwennmacher> You could certainly do it with sql. I don't know of a way to do arbitrary sql on a version upgrade.
[16:32:28 CDT(-0500)] <dmccallum54> TonyUnicon wasnt sure from the recent ticket comments… did you eventually figure out all the SQL?
[16:33:02 CDT(-0500)] <TonyUnicon> no, the core issue still is, I don't know how ssp roles relate to ssp groups
[16:33:36 CDT(-0500)] <TonyUnicon> so sql is the avenue we're going but I need to know which table it lives in
[16:34:07 CDT(-0500)] <TonyUnicon> the ssp_roles themselves live in up_permission_activity
[16:34:34 CDT(-0500)] <TonyUnicon> the fk to that table
[16:34:41 CDT(-0500)] <TonyUnicon> points to up_permission_owner
[16:34:49 CDT(-0500)] <TonyUnicon> which are uportal roles
[16:35:04 CDT(-0500)] <TonyUnicon> so I'm completely lost as to how uportal resolves that relationship
[16:37:39 CDT(-0500)] <TonyUnicon> the fk in that table*
[16:41:50 CDT(-0500)] <TonyUnicon> so for example
[16:42:05 CDT(-0500)] <TonyUnicon> when we seed perms, in this clip http://chopapp.com/#1l6o6q3w
[16:42:25 CDT(-0500)] <TonyUnicon> we define a relationship between an ssp role to ssp perm
[16:42:36 CDT(-0500)] <TonyUnicon> so I assumed there was some cross table with this relationships
[16:42:42 CDT(-0500)] <TonyUnicon> these*
[16:49:29 CDT(-0500)] <TonyUnicon> ok i figured it out
[16:50:01 CDT(-0500)] <TonyUnicon> look at import-permission_set_v3-1.crn
[16:50:08 CDT(-0500)] <TonyUnicon> that holds the answer
[16:53:23 CDT(-0500)] <TonyUnicon> it's worth noting
[16:54:00 CDT(-0500)] <TonyUnicon> I was able to delete the reference permissions without issue, which breaks uportal a little