Not able to create any security policy on newly replaced ASM

Our ASM device was just replaced. We didn't have archive and it's standalone so I'm having to manually create all the VIPS, pools, profiles, security policies, etc... I cannot create any security policy. Ideally I would prefer to just import the security policy from our other device but I've read there's a bug in version 11.5.2 that prevents this. Whenever I try to create a new policy I get this error:

Could not create Application Security Policy; Error: Could not add the Policy 'Security Policy /FamKnow/fks_vendorportal_vs'. DBD::mysql::st execute failed: Unknown column 'main_table.rest_uuid' in 'field list'

How do I resolve this?? the ASM log shows this error:

ASMConfig::Handler::handle_error): Code: 999, Error message = DBD::mysql::st execute failed: Unknown column 'main_table.rest_uuid' in 'field list' at /usr/lib/perl5/site_perl/F5/ASMConfig/Entity/Base.pm line 945

I can pull the file back and view it but no clue how I'm supposed to resolve. this is line 945 in the Base.pm file -

**$sth->execute(@subselect_values, @where_values, @having_values);**