Views
Replies
Total Likes
Hi Skye,
Thanks for posting this. I was wondering if you used the milestone text mode you referenced. I tried to use this on a project report and couldn't get it to populate as shown in the document. I attached a milestone path to the task I wanted to pull and updated the milestone ID to the one I created and the field is blank in my report. Any suggestions?
Here is the text mode I'm using:
displayname=Milestone Status
listdelimiter=
listmethod=nested(tasks).lists
textmode=true
type=iterate
valueexpression=IF({milestone}.{ID}="6176febd0041f28ae62ea31d75a3f31b",CONCAT({percentComplete},"%"," | ",{status}," | ",{plannedCompletionDate}),"")
valueformat=HTML
Views
Replies
Total Likes
hi @Luke Ramlow‚
thanks for asking! My first suggestion is troubleshoot it. Troubleshooting is one of my favorite things to do (no lie, there's a certain grim satisfaction to thrashing out exactly what's wrong).
If you hate troubleshooting, I'll tell you right now my second suggestion is always to go to the helpdesk. They can direct you with steps on what to look for and basically walk you through the troubleshooting.
What does troubleshooting look like? For me, the first thing I would do is make a task report and filter on task milestone ID = 6176febd0041f28ae62ea31d75a3f31b
If your task report pulls up the exact task you added the milestone to, then move to the next step. If it does not, do not go past this step, because you have other things you need to fix -- like troubleshooting where that milestone went to. [this part you can definitely go to the helpdesk for.]
Once you have confirmed the milestone is attached, go back to your project report, and make sure you're just pulling in that one project and no others (i.e. filter on project name =___). This will speed up the load time and give you just one row to look at.
Now, change your valueexpression in the column to something as simple as possible. e.g. instead of
valueexpression=IF({milestone}.{ID}="6176febd0041f28ae62ea31d75a3f31b",CONCAT({percentComplete},"%"," | ",{status}," | ",{plannedCompletionDate}),"")
how about
valueexpression=CONCAT({milestone}.{ID})
If your project report spits out a set of milestone IDs, you know the column "works" and all you have to do is start building back your valueexpression, one step at a time. Every time you succeed, add something new. Every time you fail, take one step back and try something else.
Successive tests might look like this:
valueexpression=IF({milestone}.{ID}="6176febd0041f28ae62ea31d75a3f31b",CONCAT("yes"),CONCAT("no"))
valueexpression=IF({milestone}.{ID}="6176febd0041f28ae62ea31d75a3f31b",CONCAT({percentComplete}),CONCAT("no"))
valueexpression=IF({milestone}.{ID}="6176febd0041f28ae62ea31d75a3f31b",CONCAT({percentComplete},{status}),CONCAT("no"))
and so on. You'll see I put in a CONCAT "no" mostly for comic relief there. It can be disheartening getting an empty cell so this reassures me something's going on... just not what I would like.
Lastly, not that you asked... the listdelimiter line should include your most favorite delimiter. This doesn't hurt anything to be empty -- it just means your linebreaks are missing. In this particular column, since you're only pulling in one milestone, it doesn't even hurt to not have a linebreak. But if you continue down this road, you're eventually going to start pulling in things and then wonder if you can have a linebreak in between them. (If you don't have an opinion I think most people use <br>)
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies