Modifying Field Types and Linked Databases
|
Availability: Pinnacle. ; Unavailability: Free, Team, Business, Enterprise; |
Wrike's Databases allows you to modify field types in your database, ensuring alignment with your Wrike workspace or source database requirements. With an intuitive interface that mirrors Wrike’s familiar user experience, you can effortlessly adjust your database structure without the need for additional training.
You must have edit permissions for the database to modify field settings. To change a field type in Wrike, follow these steps:
-
Hover over the field header, click the three-dot 1 menu.
-
Select Change field settings 2 from the dropdown.
-
Use the standard Wrike field type selector to choose the desired field type 3.
-
If you're switching to a structurally different field type (like from Text to Number), a warning dialog will appear 4.
-
Review the warning message, which details potential impacts on filters, formulas, request forms, or automations.
-
Check the acknowledgment box to confirm you understand 5.
-
Click Change anyway 6 to proceed or Cancel 7 to stop the change.
Note
After changing field types, you may need to manually update any filters, formulas, request forms, or automations that use the modified field.
The table below indicates field type conversions as compatible (✓) or incompatible (~). Additionally, incompatible conversions that trigger a warning message are marked with (✱).
|
From ↓ To → |
Text |
Number |
Percent |
Checkbox |
Date |
Duration |
Currency |
Single Select |
Multiple Select |
|---|---|---|---|---|---|---|---|---|---|
|
Text |
~ |
✱ |
✱ |
✱ |
✱ |
✱ |
✱ |
✱ |
✱ |
|
Number |
✓ |
~ |
✓ |
✱ |
✱ |
✱ |
✓ |
✱ |
✱ |
|
Percent |
✓ |
✓ |
~ |
✱ |
✱ |
✱ |
✓ |
✱ |
✱ |
|
Checkbox |
✓ |
✱ |
✱ |
~ |
✱ |
✱ |
✱ |
✱ |
✱ |
|
Date |
✓ |
✱ |
✱ |
✱ |
~ |
✱ |
✱ |
✱ |
✱ |
|
Duration |
✓ |
✱ |
✱ |
✱ |
✱ |
~ |
✱ |
✱ |
✱ |
|
Currency |
✓ |
✓ |
✓ |
✱ |
✱ |
✱ |
~ |
✱ |
✱ |
|
Single Select |
✓ |
✱ |
✱ |
✱ |
✱ |
✱ |
✱ |
~ |
✓ |
|
Multiple Select |
✓ |
✱ |
✱ |
✱ |
✱ |
✱ |
✱ |
✱ |
~ |
Note
A ✓ indicates a compatible conversion with no warning. ✱ cells indicate incompatible conversions that will trigger a warning dialog. ~ indicates the same type (no conversion).
This feature enables you to update the linked database, allowing you to redirect the field to the appropriate data source. This ensures that the field retrieves accurate and relevant information from the correct database.
Follow these steps to update the linked database for a Linked to Database custom field in your workspace:
-
Open the Relevant Space
-
Navigate to the Space where the Linked to Database custom field is located.
Note
Ensure you have the appropriate edit permissions to modify custom field settings.
-
-
Access the Field Settings
-
Locate the Linked to Database field in the space.
-
Click the three-dot menu 1 next to the field name to open the field options.
-
-
Select Change Field Settings
-
From the dropdown menu, select Change Field Settings 2.
-
-
Open Linked Database Settings
-
In the settings interface, locate and click on Linked Databases 3.
-
A list of available databases that can be linked will appear 4.
-
-
Select the Correct Database
Tip
If you’re unsure which database to link, verify with your team or workspace administrator to avoid breaking existing configurations.
-
Identify and select the correct database that you want to link 5.
-
After selecting the database, you can also choose which fields to mirror 6 from the newly linked database.
-
-
Review and Save Changes
-
Click the Save 7 button to apply your changes.
-
-
Acknowledge the Warning
-
After clicking Save, a warning dialog 8 will appear informing you that:
-
Changing the linked database will break existing connections.
-
Previously mirrored fields will be removed, and you will need to reconfigure the mirrored fields from the new database.
-
-
To proceed:
-
Check the confirmation box to acknowledge the warning 9.
-
Click Change Data Source 10 to finalize the update.
-
-
-
Verify Updated Data Source
-
Once the change is applied, the linked database will be updated, and the correct information will be displayed in the custom field 11.
-
Note
Switching to a new database will disrupt existing integrations and automations, causing them to stop working. While field data can be restored by reverting to the original database, connection settings must be reconfigured to align with the new data source.