You should apply a Cross Filter for "Contacts with Opportunities". Do this in a Contacts report rather than a Contacts and Opportunities report.
This will allow you to report at the Contact level, applying a filter based on Opportunities without including Opportunity data in the report body.
Here is what I did in my developer org. I extracted the Hours, Minutes and seconds using formula and then prefixed it with NOW() to get the Date time value. And then I extracted the Time Value. Below are the details steps:
Create a formula field of Time data type.
Put the formula as below:
TIMEVALUE( DATETIMEVALUE(NOW() + FLOOR(light002__number__c /3600) + ...
You can use this formula instead:
DATE( Year__c, Converted_Month_Number__c, 1 )
I think what you have would work if you put it like this:
DATEVALUE(TEXT(Year__c) + "-" + TEXT(Converted_Month_Number__c) + "-01")
It looks like this when its parsed:
DATEVALUE("1990" + "- " + "01" + "-01")
Instead of this, which isn't a date & ...
Little late for the person who asked, but I just had to solve this issue the problem is if you don't bring the updated ReportType along with the new reports. It seems to throw this error.
You can include the ReportType in package.xml like this:
In Composer Release 8, detail regions can be nested inside one another if the detail data is retrieved through a nested SOQL query.
Note - Building nested queries is not supported by Conga Support. This functionality is supported in Microsoft Word templates only.
You can check out this url for further reference -
You can use the Excel Connector to pull out data directly into Excel. The only option for pulling out a formatted report is the Export Formatted Report option, which exports in XLSX.
XLS is a closed-file format, meaning that developers such as those at Salesforce are not free to generate XLS files legally, and documentation on creating XLS files is ...
Based off testing by myself and Thomas Taylor, neither Custom Settings or Custom Metadata values are accessible in Row Level Formulas at this time.
A workaround to referencing this data in a Row Level Formula is to create a Formula Field on the Object referenced in the Report that pulls the Custom Setting field or Custom Metadata field required.