Getting # in PBI Report

[Anonymous]

Hi Friends,

We are implementing Power BI in our organisation as the reporting tool. The data source is BW4HANA.

we are trying a PoC to establish we can build a hierarchies in PBI using BW Query. We are using "Direct Mode". To create a hierachy in PBI BW query is providing 4 fields Node1,Node2,Node3 and Node4. There are seven rows in the BW query output.

Node1 is the highest Node and Node4 is the lowest.  There are values in first three fields Node1 to Node3

Values are populated in all 7 rows for Node1 to Node 3, however in Node4 values are populate only in the first 3 rows. In the PBI report where there are values for a Node4 there is no problem, but where there are no value in Node4 we are getting "#". 

Can someone please advice how to eliminate "#" ?.

Really appreciate your help.

Regards

Naveen

[Anonymous · Accepted solution]

HI @Anonymous,

If you are working with direct query mode, the current power bi does not support your operation or replace the table records.

Did you work with the bw data connector? If that is the case, you can try to add a query in the advance option to filter or replacement on the result.

Use the SAP Business Warehouse (BW) Connector in Power BI Desktop - Power BI | Microsoft Docs
Regards,

Xiaxoin Sheng

[Anonymous]

Hi Ibendlin,

Thank you for your response. 

Yes, there is no Value in Node4. In BW we cannot pass NULL to so the value will be empty where the is no Value in Node. Since we are usig "Direct Query" I am told that by the Power Bi resource that it is not possible to applying any transformation is PBI to replace empty value with Null. So want know if it is possible to replace # with blanks by doing some config/steeings instead of writing DAX?.

Regards

Naveen

[lbendlin]

Try using a measure to replace the Node4 values with BLANK()

[lbendlin]

Are you sure there is no value in the rows for Node4?  Or maybe an empty string is provided? Ideally you will want to replace that with NULL. Use a Power Query replacer (unless that is not allowed in your direct query scenario)