Here's a few screenshots showing how to do this easily. Red highlights indicate text that need be deleted. Yellow highlights show what need to be added. It's super easy once you have a few edits done:    

assuming this is an issues/task/project report the below will work:group.0.linkedname=enteredBy group.0.namekey=view.relatedcolumn group.0.namekeyargkey.0=enteredBy group.0.namekeyargkey.1=homeGroup group.0.namekeyargkey.2=name group.0.valuefield=enteredBy:homeGroup:name group.0.valueformat=string t...

Haven't tested any of these calcs but the first thing that caught my eyes was that you're missing the "DE:" in your calculations. Every instance of the Date End field should appear as follows:  {DE:Date End}

Might be best if you move the Line of Business field into the form instead of using the Queue Topic. I understand there may be downstream effects doing this depending on how long you've used that format.

This is not possible.  The Queue Topic does not become associated with an object or the form until the form is submitted. There's no way for the form to know what queue topic was selected until after it's submitted.

I kept testing this and couldnt get the wildcard to work in the calculation. I decided to look at the documentation and found this snippet:  "Wildcard filter variables are not supported when referencing nested collections in a calculated column". Unless Im misinterpreting the verbiage it looks like ...

Looking at the API Explorer I'd try using {assignedToID} not {assignedTo}.{ID}.

Thanks for the tip! Just what I needed. I'll test it out

Hi all - I was looking at our timesheets and noticed that they did not autogenerate like they normally do for us on the 1st of the month.  Normally, the following month's timesheets (July) autogenerate when we reach the 1st of the prior month but it looks like that didnt happen this month.  Anyone e...

@TamBou, @CarolH  Just noticed that ours didnt autogenerate for the month of July like they shouldve. Did you contact support? Have they responded?