cancel
Showing results for 
Search instead for 
Did you mean: 

SAC Live Data Connection to SAP BW 7.50 - No available descrition due to server error in Filter

dohaidang_le
Participant

Dear all,

we are using SAC Version 2020.21.14 building Live Data Connection to SAP BW 7.50 SP 16.

While using the filter line component and calling up dimension members for filtering, sometimes we run to this error

After closing and reopening the filter popup, or switch on and off the "Show unbook member", the error disappears and the dimension members are shown.

Analysing in DEV mode of the browser shows that, to call up the dimension members, the SAC client sends a request with header field firefly-cache-hints, which is not allowed by the CORS policy of the server. Thus the request is rejected by the BW server.

It is strange, because the rejected header field firefly-cache-hints is not always sent with the requests, only sometimes. But when it happens, it really causes unconvinience to users.

Anyone has the same problem and how to you fix it?

Thanks

dohaidang_le
Participant
0 Kudos

Sorry, it's not solving my problem. We already solved the problem with same-site cookies by doing as suggested here Direct Live Connections in SAP Analytics Cloud and SameSite Cookies - SAP HANA Journey | SAP HANA Jo...

DebjitSingha
Active Contributor
0 Kudos

One you implemented is backend soln and the browser based option is front end. Both targeting same issue. Its just two different approach. Back end option is obviously the best solution, though it is recommended test scenario with browser change first. Reason why I asked you to test it first.


are you saying you tried browser based change and it didn’t worked?

Accepted Solutions (0)

Answers (1)

Answers (1)

yorur_oz
Explorer
0 Kudos

Hi Do Hai Dang Le,

Have you solved the problem?

https://apps.support.sap.com/sap/support/knowledge/en/2748971

This note may be useful for you.

dohaidang_le
Participant
0 Kudos

Actually I'm about to add "firefly-cache-hints" to the setResponseHeader Access-Control-Allow-Headers in the rewrite-file. I'm just wondering why SAP adds this header into the request and why it is needed.