Felix M Joseph

I added "Save To Cache And Update Related Metadata processor". It was not saving idv3 to cache after saving. Idv3 is needed in ProgramOrderablesPriceHistory table.

I added "Save To Cache And Update Related Metadata processor". It was not saving idv3 to cache after saving. Idv3 is needed in ProgramOrderablesPriceHistory table.

How to know that this is numeric or currency? Because this field is not available in v2 database. I added default value to TEXT because it mandantory

How to know that this is numeric or currency? Because this field is not available in v2 database. I added default value to TEXT because it mandantory

TZUP-213 Requisition templates
TZUP-213 Requisition templates
TZUP-219 Ftp configurations
TZUP-219 Ftp configurations
TZUP-207 Role Assignments
TZUP-207 Role Assignments
Can you review again. I have solved also duplicate issue it was caused by case sensitive.

Can you review again. I have solved also duplicate issue it was caused by case sensitive.

In v2 users table at verified column there is data which have null value instead of true or false. And v3 verified is mandatory. And most of them it seem was added and never used. May be if we can ...

In v2 users table at verified column there is data which have null value instead of true or false. And v3 verified is mandatory. And most of them it seem was added and never used. May be if we can clean them first before running scripts.

There is a lot of username duplicates in v2 users table. It seems there is no unique constraints. It was generating constants exceptions in v3 users table.

There is a lot of username duplicates in v2 users table. It seems there is no unique constraints. It was generating constants exceptions in v3 users table.

TZUP-207 Users
TZUP-207 Users
Supervisory nodes TZUP-181
Supervisory nodes TZUP-181
TZUP-207 and Supervisory nodes
TZUP-207 and Supervisory nodes