PhilD Member

Thanks! A brilliant solution... seems to work very well for what I needed. I added the year in front and the only quirk is that the handful of entries having a date prior to the first pay period start of the year are grouped into "period 26" which makes sense. I just used a sort to move this group all the way to the left…

When I try to schedule a card that is filtered by relative time (i.e. Last 10 days), the report is delivered for the entire date range. Tried everything but cannot get this to work (never could since we started using DoMo).

Thanks @GrantSmith The locations come from a table in the app so they are the same. Funny thing, I actually created a new card from scratch and my first attempt worked (I thought that it should). I had both cards open side by side and verified everything was absolutely positively identical and the first on kept giving me…

While this seemed to give the results I desired, there is no way to filter by any of the many dimensions so this won't really work. Still looking for some direction on this, thanks.

So I did achieve the results I desired in this case but not sure if this is the most efficient design pattern. In my Data Flow, I created a new table Select`LocationID`,`Location`,COUNT(DISTINCT `ResponseGroupID`) as 'Distinct ResponseGroupID'From `ajh_rounding_recursive_final_output`Group BY `LocationID` Then joined this…

This is huge issue that makes me wish I never had to use this platform. Making changes to 20 different card's drill down views, when each is identical, is really not the type of work I want to be doing.

This is proving to not really be a usable solution. This is too bad because DoMo could have been extremely useful in our organization. We have lots and lots of Qualtrics surveys and the built-in Qualtrics reporting is not as good as DoMo but I have spent some time trying to figure this out and I'm pretty much convinced…

Thanks @MarkSnodgrass ! I haven't had time to get back to this but I am anxious to put this information to use. I appreciate your having taken the time to reply. I will be sure to update this thread with my experience.

Hi @DDalt Unfortunately I haven't actually had time to try this but it is on my list. One thing that comes to mind is that to do this would require pulling each survey's data separately (as each would have a different number of questions). Not a deal breaker, just an observation. I will definitely be doing this and will…

I did see the "collapse" and "uncollapse" options in the ETL transform but could not seem to get the options it supplied to do what I needed. Based on your feedback, this is likely due to not having a unique ID. If I'm understanding you correctly, it sounds as if the truly unique ID would be used to iterate the function…

Thanks @ST_-Superman-_ Yes, there are other columns as my example was meant to just communicate what I needed. Here is a full list of the columns returned by the 'Survey Responses' report on the Qualtrics API Survey NameSurvey IDAnswer ValueRecipient First NameIP AddressStart DateQuestion KeyQuestion IDLocation…