Below are some Q and As to help you in troubleshooting common issues with using Project Requests.
When I create the new project from an approved request, some or none of the fields that are set to "Map To" copy over.
If no files fields, files, Spec Sheets, Ect. copy over to the new project, and then something occurred when you clicked Create Project, and none of the data carried over into the New Project screen, you should double check that the proper fields are already populated in the New Project screen before you save that into an actual project. If you see data missing, close the New Project screen, and click Create Project from the request once more.
If only some of the Mapped fields are populated, then most likely the map to option is not correct. Also, check that the data is valid for both sides. For example, if you have a dropdown list, make sure both the Project Request Custom Field and the Project Custom Field have the same exact list. In some cases, when changes are made on one side or the other, you may need to unmap the field, save the field, then remap the field.
When I click Next on the first page to fill out of the request form I get a screen that says "/application error"?
This occurs when you populate a field with invalid data. For example, if you manually populate the Client ID field with TESTCO, yet you do not have a client in the system with that ID, then when you click next, you will get this error. Another example is date fields. If you enter a date manually that does not conform (i.e. 1.1.2010) to the date format of the system, then you will get this error.
Can I use Project Requests with Opportunities?
No. These are two different processes for project intake.
When will the project request interface get updated?
We hope to address this down the road with the Platinum interface.