cancel
Showing results for 
Search instead for 
Did you mean: 

Publish to workspace works from Desktop but not using REST API

 

 

 

 

 

 

Setup:

A report using web.content to get JSON document. 

JSON Document has some optional data elements.   

The report is developed using data with all elements present. 

 

Symptom:

For cases when all data elements are returned, the report can be published using either the REST API or from the Desktop.   The report and the data set is created and the data model can be refreshed. 

 

For cases when optional elements are missing, the reprot can only be published using the Desktop. Publishing using REST API will fail, reporting a missing field in the model.   Using the REST API, the report will be created in the workspace along with a dataset shell, but no data will exist and the report cannot be refreshed.    Publishing from the desktop in this scenario is successful, the report and dataset are created and the report can be refreshed. 

 

There is some difference between publishing using the desktop and the service, where the service is not able to accomodate missing data elements when publishing.  

Status: New
Comments
Frequent Visitor

Deeper analysis (decomposing the .pbix) shows the error occuring when transposing rows in a small table into columns.  Two optional rows are missing, causing the resulting table columns to not match hardcoded values in the 'DataMashup' file.  

 

Excerpt from DataMashup file; offending columns highlighted in red below: 

 

     Config/Package.xmlPK-    ¦zzLÊ髤   é                õ   [Content_Types].xmlPK-    ¦zzLû-pC›   F               æ  Formulas/Section1.mPK         Î      <?xml version="1.0" encoding="utf-8"?><PermissionList xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><CanEvaluateFuturePackages>false</CanEvaluateFuturePackag...    ü¤ <?xml version="1.0" encoding="utf-8"?><LocalPackageMetadataFile xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><Items><Item><ItemLocation><ItemType>AllFormulas</ItemTyp... /></ItemLocation><StableEntries><Entry Type="Relationships" Value="sAAAAAA==" /><Entry Type="QueryGroups" Value="sAQAAAAAAAADuX5pv2x+cQZuj1Gs4f9dlClBhcmFtZXRlcnMAAAAAAAA=" /></StableEntries></Item><Item><ItemLocation><ItemType>Formula</ItemType><ItemPath>Section1/Client</ItemPath></ItemLocation><StableEntries><Entry Type="IsDirectQuery" Value="l0" /><Entry Type="NameUpdatedAfterFill" Value="l1" /><Entry Type="ResultType" Value="sTable" /><Entry Type="BufferNextRefresh" Value="l0" /><Entry Type="FillColumnNames" Value="s[&quot;clientid&quot;,&quot;companyName&quot;,&quot;reportingCcy&quot;,&quot;forecastStrategy&quot;,&quot;referenceCcyDetermination&quot;,&quot;decisionStrategy&quot;,&quot;tradeConsolidationStrategy&quot;,&quot;numberFormat&quot;,&quot;defaultNumberOfPeriods&quot;,&quot;netExposureThresholdDefault&quot;,&quot;netExposureThresholdDefaultCcy&quot;,&quot;hedgeRounding&quot;,&quot;tradingCounterparty&quot;,&quot;tradingEntity&quot;,&quot;externalIds&quot;]" /><Entry Type="RelationshipInfoContainer" Value="s{&quot;columnCount&quot;:15,&quot;keyColumnNames&quot;:[],&quot;queryRelationships&quot;:[],&quot;columnIdentities&quot;:[&quot;Section1/Client/Transposed Table.{Column1,0}&quot;,&quot;Section1/Client/Transposed Table.{Column2,1}&quot;,&quot;Section1/Client/Transposed Table.{Column3,2}&quot;,&quot;Section1/Client/Transposed Table.{Column4,3}&quot;,&quot;Section1/Client/Transposed Table.{Column5,4}&quot;,&quot;Section1/Client/Transposed Table.{Column6,5}&quot;,&quot;Section1/Client/Transposed Table.{Column7,6}&quot;,&quot;Section1/Client/Transposed Table.{Column8,7}&quot;,&quot;Section1/Client/Changed Type.{defaultNumberOfPeriods,8}&quot;,&quot;Section1/Client/Changed Type.{netExposureThresholdDefault,9}&quot;,&quot;Section1/Client/Transposed Table.{Column11,10}&quot;,&quot;Section1/Client/Changed 

Community Support Team

Hi @jbrandt,

 

I would suggest you file a support ticket here for such scenario.

create ATicket

 

Best Regards,

Dale