Hello,

Recently we made a model change - integrated "NSSR Object" to "Projects". Model allocation looks OK, but we are seeing an issue with "IT Management - Project Details" which is Apptio Out of the Box Report. Please see the attachment for further details.

Error Description -  Please provide a row or column to cross reference 'NSSR to Projects Stage' and 'Projects'.

If any one faced a similar issue, please let us know what we should do.

@Taryn Kane , @Debbie Hagen @Jenny Goodwin Srikanth Satakopan @Ericka Norman @Pablo Santana

Thanks & Regards

Babu HM

Babu,

Based on looking at the report, the report is leveraging the Projects Object.  When you were adding the additional object it sounds like you were adding it before the projects object.  Do you still have costs going to the project's object?  Also, is there a relationship between NSSR and Projects object?  If not, I believe that you'd have to leverage the join and combine the tables on a common attribute.  

Also, has there been any customization to the report where you added a column from the NSSR object?

Cheers,

Ryan

Hello Babu,

Do you still have the Projects Object?  Did you rename the Projects object to NSSR or did you add NSSR as an intermediary object before projects?  

Thanks,
Deb

Hello,

Thanks for quick response. I'm adding "NSSR Stage" object before moving the cost to "Projects".

Both Projects and NSSR are connected via common key. Also for the Project Details, I'm not pulling anything from "NSSR" object, basically "Project Detais" OOB report is untouched. Also I'm able to trace the cost from "NSSR Stage" all the way to "Applications"

Thanks & Regards

Babu HM

Babu,

In regards to the picture of the model thanks!  By chance how are you creating the other master data sets for Projects Stage and NSSR?  Are they transforms of the projects data or some part of those datasets.  

Looking at the error message, I'd double-check with looking at the full data path to make sure that you are not pulling potentially any of the columns from those objects.

Can you grab a screenshot of the table with the full datapath?

Cheers,

Ryan

Hello All,

Thanks for the responses and tips. We got this fixed after our CSM (@Taryn Kane) pointed us in a right direction. Since "IT Mgmt --. Project Details" is a drillTo report and it happened that there were few calculated fields - Cost YTD and CapEx YTD which weren't related to NSSR Stg or Projects. This spurred an issue when we connected "NSSR Stg" to Projects. So the resolution is to take out Cost YTD and OpEx YTD and pull in "Cost" from calculations perspective and we changed the "Value Field settings" to do YTD calculations as a new field.

Thanks & Regards
Babu HM

Way to go @Taryn Kane!  And thanks @Babu Hussainsab Mehrunnesa for following up with the resolution on the thread!  That's a great way to help others benefit from your learning and truly embraces the concept of Community.

Hello All,

I want to extend this thread since we noticed somewhat a different behavior with "Project Details" report. As described in my previous thread the exact model change is I just added a NSSR to Project Stage object and moved the cost to the existing Projects object. On the "Project Details" report we have not pulled any column from "NSSR Stage" object, but even then on the adhoc perspective we see both "Projects and NSSR to Project Stage" are joined. (Please see the attachment)

Because of this default "drillTo" behavior (which we didn't intent) the Project Details report shows only the projects match between NSSR Stage and Project object. Ideally it should display all the projects available at "Projects object".  I'm not sure If I have done something in the model which would have caused this behavior of two tables joining the adhoc table.

@Taryn Kane, @Debbie Hagen @Jenny Goodwin @Ryan Paul  Srikanth Satakopan @Ericka Norman

Regards

Babu HM

The drill will be forced if you are filtering/showing a column from the NSSR to Projects Stage Object.

Hi Babu,

In your snapshot, pull Project Name out of the rows section in the Ad-Hoc Query Configuration Box. You'll see the NSSR to Projects Stage object fall out of the top of the box and the table will show an error (only because there's no grouping rows, we'll fix that with the next step).

Then go into the Data perspective and grab Project Name from the Projects Master Data and put it into Rows where it was before. 

The table will no longer be a drill at this point (confirm by seeing only Projects listed in the top section of the ad hoc query box).

Thanks a lot @Taryn Kane, it worked. I understood the mistake was "Project Name" was not pulled from the right perspective.

@Mark Nealey  @Debbie Hagen Srikanth Satakopan @Ericka Norman