Smarter Conditional Mapping for Request Forms Using Custom Fields

In our enterprise, we manage two key custom fields used across all of our ad hoc request forms:

• Client
• Client Product

These fields drive our conditional mapping within Wrike request forms. When a user selects a client and product, the request automatically lands in the correct Wrike space → product folder → year of work. This setup creates a streamlined experience for our teams and keeps work organized by client/product/year.

However, here’s the challenge:

• We have 10+ ad hoc request forms, each supporting different disciplines.
• Any time a client or product changes, every single form’s conditional mapping must be updated individually.
• Worse, changes made to the custom field itself can break the existing conditional mapping, requiring 10+ manual updates just to restore functionality.

Proposed Solution:
We’d love to see conditional mapping controlled at the custom field level, rather than at the form level. Ideally, we could:

1. Assign a landing location (folder/project) directly to the custom field value.
2. If the landing location changes, we update it once at the field level and push it across all related request forms.
3. Include an opt-out option for specific forms, allowing us to override the global mapping logic when a form’s workflow differs from the standard.
4. Bonus: Allow spreadsheet uploads to bulk-manage destinations since we already track clients and products this way.

This improvement would significantly reduce admin time and ensure consistency across all our request forms, while still giving us the flexibility to customize where needed.