If you filter not the AssignedTo, but the Assignments... assignmentsUsersMM:ID=$$USER.IDassignmentsUsersMM:ID_Mod=in and then have the collections column...link.linkproperty.0.name=IDlink.linkproperty.0.valuefield=IDlink.linkproperty.0.valueformat=vallink.lookup=link.viewlink.value=val(objCode)listd...
While this is a column for the Parameters... it shows the Name and the Label as well as the position the field holds on the form listdelimiter=<br>listmethod=nested(categoryParameters).listsname=[Position] - Field Name // Labelstretch=100textmode=truetype=iterateusewidths=truevalueexpression=CONCAT(...
I actually have updated my formula too... ROUND((((DATEDIFF({entryDate},DATE(CONCAT("1/1/",YEAR({entryDate}))))+1)-(8-DAYOFWEEK(DATE(CONCAT("1/1/",YEAR({entryDate})))))-DAYOFWEEK({entryDate}))/7)+2,0)
Unfortunately they do change, thus the desire to be dynamic. Currently we are bringing them in when initially instantiated. Its actually a pretty involved process of automation. I just did not want to have to add a new Scenario to maintain synchronization as well.
Description - Add ability to Navigate to any field on the convertedOpTask in calcuolated fieldsWhy is this feature important to you - Can create View Only custom forms that link from a Project to a converted issue to the original projectHow would you like the feature to work - Add ability through AP...
In Reporting you can link between a Project and the convertedOpTask object and so can then also "Navigate" to the Project from which it originated. But while the Calculated Field area seems to allow you to enter it in a similar fashion, when you go to save the form, it provides a message that the fi...