Changing text field from "local" to global field

2

Hi everyone,

this is just a short list of actions I had to do, when I switched from a "local" text field, WFD_AttText1, to a global WFD_AttText1Glob:

1. Fixing Start Subworkflow actions
Due to the change of the field type the assignment was "lost". Internally the action uses the database name, so it's obvious, that the assignment of field {690} to field WFD_AttText1 is no longer valid.
Configuration after correcting the assignment
<field>
<attribute>WFD_AttText1Glob</attribute>
<value>{690}</value>
<override>true</override>
</field>
There was no "problem" with the following actions: Update attachment, SDK action, Change value of single field, notifications.

2. Saving report views
I had to save each report view to show the new column. It was sufficient to click on the view and hit the save button.

3. Data source
I had to remove the field, add it again and correct any usages, where the old column was used.

4. Copying values in the content database
An archive database was not involved.

Update WFElements
set WFD_AttText1Glob = WFD_AttText1
where WFD_DTYPEID
in (
select DTYPE_ID
from WFDocTypes
where DTYPE_Guid in ('31d8115c-a51a-451c-bdfd-ee17de78ab8c')
)

Update WFHistoryElements
set WFH_AttText1Glob = WFH_AttText1
where WFH_DTYPEID
in (
select DTYPE_ID
from WFDocTypes
where DTYPE_Guid in ('31d8115c-a51a-451c-bdfd-ee17de78ab8c')
)


Remarks:
This is no official guide, just the steps I had to take. If you are in a similar situation you can use this as a guideline but verify it on your system:
1. Make a backup of the databases
2. Have another environment with the same process ready, so that you can check the usages tab of the field
3. Tests

Best regards,
Daniel