Hello,

Sorry to keep writing posts, we are just running into a lot of random errors lately as we have been rolling the portal out to a lot of our clients. The newest issues I am running into is this: I have a client that has 3 seperate projects under their project Tree and I want a different person to get assigned depending on the project they pick, looks like this:

Main Project

    - Sub Project 1

    - Sub Project 2

    - Sub Project 3

The "Restrict view to" and "Allow Add/Edit in" settings are set to "Main Project", we have a project drop down on the field template for that level. Each sub-project has its own Field Template (Each of which assigns to a different internal user based on the project specs), for some reason, even after I select a project, and I SEE the field template load, it is still not changing the "assigned to" field.

My Main Project assigns to no one, but the other 3 projects all have a field template that changes the "assigned to" field to an internal user, but the field template is not activating that field. All of the available fields change when I select the projects, which means to me that it is picking up that the new field template that it should be using based on the project, but that field is never being populated regardless of which project I select.

 

Suggestions?

 

Thanks

Chris
 

The field template default values are only applied the first time the add window/page is opened.  If you change the project, and it causes the field template to change, the new field template's default values do not get applied.  This is by designed, and it works that way because we did not want these default values to overwrite any values that a user would have entered/selected. 

The behavior you want should instead be done with workflow step actions.  You can set up a workflow with different steps that assign the item to different users, and assign each of those steps to each of the projects as the 'Place new items into' workflow step.  If you check both the 'Enforce workflow step' and the 'Restrict new items to selected step' checkboxes for the projects, then when a user/customer changes the project, the item's workflow step is automatically changed and the step's actions are performed to set the assigned to user.

The bad news is that there is currently a bug that causes the workflow step to not be properly set when changing the project.  This will be fixed in the next release, 8.1.

---

Dan Suceava
http://www.axosoft.com

Thanks Dan, what is the ETA for 8.1?

We don't have an exact date yet, but it will probably be towards the end of Q2.

---

Dan Suceava
http://www.axosoft.com