Request forms - Autopopulate/map to custom fields on a task folder

Hi there.

The Request Form feature is a great tool. However, there is limited option to map to fields on the task that is created by the form. Currently, it is ONLY Title, Description, Start Date or End Date.

The ability to map a form field to a custom field on the task would make this tool so much more useful and productive.

When you create a form, you have to tell it which folder the task goes in, so it should provide an ability to map any form field with a custom field that is defined on the target folder.

Please consider making this change

Regards,

Tony Gill

Find more posts tagged with

Launched

Status: Launched

Comments

Paul Copping

Agree with this

Cathy Coia

I also agree this would be a very helpful addition to the request form

Permanently deleted user

Hi everyone! Thank you for sharing, it's great to hear your thoughts about how the current functionality can be expanded, and this is a great idea.

Stacy Perrus

Yes, this is the one feature we need to be able to replace our Sharepoint form and workflows with Wrike and become a paying customer.

Darius Family

Yep this is much needed! We have forms with multiple date input fields, which we'd love to map to the relevant custom date fields in a task

Beat Z'graggen

It would really help not having to copy/paste content already entered in custom fields

Miquel Brunet

This feature would be much appreciated!

We would like to know if this feature is in the roadmap of the request forms.

Thank you!

Paul Copping

Dynamic / Lookup Entry Fields -

Also it would be useful to be able to add fields where answers are dynamically linked to information already in Wrike, in a similar way to creating tasks happens know.

with auto search filtering which is already built into Wrike.

Examples:

User field selects from current Wirke Users.

Project or Folder field selects from dynamic list of current folders / projects

Custom statuses.

others.....?

Permanently deleted user

Hi Miquel and Paul! Thanks for weighing in on this request, these suggestions are fantastic. While there's no timeframe to share yet, our Product Team is looking at ways to enhance Request Forms, and your ideas and votes help us understand the popularity of these requests. @Paul, I also wanted to say that I really like those examples, this would definitely be useful.Thank you for sharing your insight!

Richard Lomer

Strongly in favour of this update - currently a frustrating gap.

Mike Robinson

It would be great if I could share custom fields with request forms. I have set up a request for change workflow, so that users can request IT developments and the information captured on the form, only appears as text on a new task.

The issue is, that I then have to spend time, copying the same information and applying it against the task in one of my custom fields.

I need to be able to filter my work by custom field [not by tagging or folders]

Process looks like this:

1) The user completes a request form

2) The form is created as a task - but the information is shown on the task as text

3) I then have to copy that text, and apply it to the custom fields

Permanently deleted user

@Mike, thanks for taking the time to copy your comment over to this post. Wanted to mention once more that I love the screenshots and how you illustrated this use case.

Dru Michaels

Custom Fields in a Request form could be of benefit for sure.

thx

Janet Atteberry

Agree with all of the comments above - using the forms is a great way to get requests. I like the features of indicating who it's assigned to and what folder it gets tagged to. Much like @Mike' s illustration above though, I have the user enter the data into fields but once the form is submitted, I have to manually copy and paste the types and sources in particular to get any sense of the volume.

Additionally - the submission date doesn't prepopulate into the start date, so once the form is retrieved the user has to put in the date, the workflow and the end date (we have a start and end date due to needing TAT but it is in the form, not in the Task or Project).

I would also like to be able to assign a form to a group instead of a specific user or users. We have groups where it may need triaging - at this time one or two people have the responsibility and they must remove or add assignees once they retrieve.

Prayes Majmudar

I agree there are so many applications if this type of feature were to be enabled.

Jamie Baddeley

I agree with this suggestion. At the moment I'm using the API to extract the information from the task description and then populate the customFields with the right information which works but is far from ideal.

Tom Ho

I saw this email this morning

Dynamic Forms Adapt to Customer Needs

Display different questions, based on an initial response.
Manage fewer forms, while collecting better requirements.
Requesters experience more relevant forms.
Target the availability of forms to users and groups.

Any more help info for this? Is this just form fields that appear when specific answer is selected?

Thanks

Permanently deleted user

Hi Tom, thanks for reaching out here! Dynamic Forms are the latest release to our Requests functionality, and they allow you to enable conditional inputs which trigger different pages to be displayed based on an initial drop down response. To start using this functionality:

Access the Form Builder in Account Management.
Scroll to the bottom of the Form to add more pages. You can later select these pages to redirect users there, based on the answers they give.
Add dropdown type questions. Click the branching icon next to each answer to set up a conditional formatting rule:

Happy to answer any questions!

Raul Guerra

Would like to map fields on request forms to custom fields (columns) we use to organize tasks. Currently, the request form can only send info into the task description area where it then needs to be copy/pasted into the corresponding custom fields (columns). This seems like an easy modification on your back end that I imagine users of custom fields would appreciate and benefit greatly from.

Permanently deleted user

Raul, I appreciate your insight, thank you for sharing your thoughts about this and weighing in on the request!

Olga Batygin

The ability to export all answers from a form into a .csv would be also fantastic

Stephanie Westbrook

Hi Olga! I would love to know if there's something specific you do with the data once it's in a .csv file? We do have the option to export tasks to excel. So if you have all of your Requests landing in a specific Folder, you could then export the tasks from that Folder (the submitted Requests) to Excel.

Dawn Hepper

I agree with @Olga on the export request. We are a new customer in the process of onboarding, and our Wrike contact led us to this thread. We are currently planning to use the dynamic fields on the request forms to capture information critical to the design process that we would later want to append with performance data for this same campaign. Right now, it seems we can only export information from custom fields, which doesn't allow us to use the dynamic field feature. This is a significant issue for our team that may need to do duplicate work to capture this information in yet another system, and shouldn't be necessary, since all the information lives in form fields as part of the initial intake process. I'd love to know if anyone has found a solution to this issue. Thanks!

Laura Walz

This is a necessity for us to do business! We need the fields populated from form requests exported in Excel in order for us to append results and sales data to our project data. Currently we have a lot of manual data entry and we are looking to find a solution. The advantage of the request form is that it is standardized and dynamic, because we have quite a few employees using a good number of fields. Please let me know if you have found a successful way to export! Thank you.

Colleen Farrell

I agree I think this would be extremely beneficial to have!

Stephanie Westbrook

Hi @Dawn and @Laura you can export tasks to excel and that export includes data from the description field (which is where most answers from Request forms go) but I understand that the format may not be ideal for your team. Also, I appreciate the details from both of you regarding how you work with the data once it's exported, it helps our team better understand your use case.

Josef Severson

Data entered into a request form is important information. The ability to have these request fields mapped to an exportable field in addition to the text-based description field is valuable to my business and the positioning of Wrike in my organization. To be honest, I was surprised to find this was not possible. Wrike development team: please prioritize this option both in CSV export as well as in the API.

Permanently deleted user

Hi everyone, thanks for commenting here! Request Forms are one of our newer features, and our Product Team continues to work hard on improving and enhancing this functionality. While it isn't possible to fulfill all requests right away, the discussions which take place on the Community are definitely an important resource for our Product Managers when it comes to planning the product roadmap, and your votes and comments help learn about the popularity and importance of these requests. Thank you everyone for taking the time to share your thoughts and ideas with our team here, we'll make sure to keep this thread, as well as others, updated as we work on new additions.

@Josef, I'm really interested in the data you'd like to pull through the API - are you referring to being able to pull all the data right at the time of Form submission?

Stephanie Westbrook

Hi @Olga, it looks like your reply got sent to our Support queue instead of to this thread, but I'll go ahead and reply here. I understand now, using graphs and running Excel based reports makes sense. Does the option to export tasks to excel help in your case?

Olga Batygin

Hi Stephanie,

No, not really because we need the data in the fields, not the tasks exported. thanks for looking into it

Olga