To GoodData homepage

Replies posted by Ulku Kijasev

18 Replies

Z
zmazulaKnown Participant
asked in Dashboards and Reports

New dashboard/insight bug in a child workspace

Hi Zoltan,Sorry for not returning to you earlier. This issue was fixed with GoodData.CN Release 2.0.0 which was done on 14.Jul.2022.Best Regards,Ulku

15
U
GoodData Employee
1 year ago
Z
zmazulaKnown Participant
asked in Dashboards and Reports

New dashboard/insight bug in a child workspace

Hi Zoltan,The issue has been fixed but it will be deployed with Gooddata CN Release 2.0.0 which is planned on 14.Jul.2022.Best Regards,Ulku

15
U
GoodData Employee
1 year ago
Z
zmazulaKnown Participant
asked in Dashboards and Reports

New dashboard/insight bug in a child workspace

Hi Zoltan,The developers found the problem, they will try to fix it tomorrow. But it needs to be tested and released. I will return to you again about the official delivery date. Thank you,

15
U
GoodData Employee
1 year ago
Z
zmazulaKnown Participant
asked in Dashboards and Reports

New dashboard/insight bug in a child workspace

Hi Zoltan,I have created a ticket for this bug to our engineering team. I will inform you as soon as the bug will be fixed.Thank you,Ulku 

15
U
GoodData Employee
1 year ago
Z
zmazulaKnown Participant
asked in Dashboards and Reports

New dashboard/insight bug in a child workspace

Hi Zoltan,No i used the existing insight from the parent workspace. I tried to create new insight in the client workspace but i got another error. I will check this with engineering and return to you. Thanks.

15
U
GoodData Employee
1 year ago
Z
zmazulaKnown Participant
asked in Dashboards and Reports

New dashboard/insight bug in a child workspace

Hi Zoltan,I could not reproduce the error when i followed the steps which you clearly defined. I used GoodData CN version 1.7.2 and Chrome version 100.*. In the attachment you can see “Price by customer” is the inherited dashboard from parent workspace. It works with filters. And the “Dashboard client1” is the successfully created dashboard in client1. I have three client workspaces. So when creating dashboard in client project, i did not receive error you described. It was successfully created. Could you please try with version GoodData CN 1.7.2. Thank you,Ulku

15
U
GoodData Employee
1 year ago
d.novikov
d.novikovParticipating Frequently
asked in GoodData.UI

How to configure CORS for the /api/profile path?

It should return you response 200 OK

13
R
GoodData Employee
1 year ago
d.novikov
d.novikovParticipating Frequently
asked in GoodData.UI

How to configure CORS for the /api/profile path?

We see that you’re getting error response 403 to GET request to /api/profile. This means you still have problem in authorisation part. You most probably have invalid CORS configuration, so your API requests are rejected because they don’t allow localhost origin. The fix could be adding https://localhost:8443 to allowedHosts in the organization configuration, or you can add https://localhost:8443  to nginx.ingress.kubernetes.io/cors-allow-origin as explained above you can choose where to add depending on your needs. But it seems that https://localhost:8443 was not added as allowed origin in your CORS configuration.

13
R
GoodData Employee
1 year ago
d.novikov
d.novikovParticipating Frequently
asked in GoodData.UI

How to configure CORS for the /api/profile path?

Hi,In order to help workaround authentication errors, some colleagues used here workaround by starting the frontend app like this: REACT_APP_DEV_TIGER_API_TOKEN=YWR… yarn start. Could you please try this and let us know if it solves your problem. Maybe it could help.Thank you,

13
R
GoodData Employee
1 year ago
d.novikov
d.novikovParticipating Frequently
asked in GoodData.UI

How to configure CORS for the /api/profile path?

Hi,Could you please give us more details about what happened. Did you manage to successfully log-in and it failed on communication during the GET /api/profile. Or even the login wasn’t successful for some reason? Could you please send us a screenshot from the browser where the error occurred, as well as the failing API request and the response (at least the status code and not sensitive response headers). If you can provide us also logs it would be good.Thank you,

13
R
GoodData Employee
1 year ago
d.novikov
d.novikovParticipating Frequently
asked in GoodData.UI

How to configure CORS for the /api/profile path?

Hi,Have you set up the organization as described in here. Did you prepare the organization.yaml and setup the administrator account in it? And after creating the organization then you can setup the authentication for configuring other users, which are composed of steps Creating bootstrap token, Setting up an OIDC identity provider and mapping users to organization as in doc. Please let us know if you have followed the steps for creating organization and administrator account.

13
R
GoodData Employee
1 year ago
d.novikov
d.novikovParticipating Frequently
asked in GoodData.UI

How to configure CORS for the /api/profile path?

Hi,CORS headers were originally set up with the same value of Access-Control-Allow-Origin for all organizations using nginx ingress annotations in Helm chart values  (in ingress.annotations key).Since GoodData CN version 1.7.0, the configuration can be done the following way:if custom UI apps are running on the same domain as Organization, no extra setup is needed. If custom UI apps run on the other domain and this app is somehow used for multiple organizations, customers still can use the old method using ingress.annotations  that will be automatically applied for every existing and every newly created organization automatically. If custom UI apps run on the other domain and this domain needs to be different for every organization (like app-prod.example.com for organization prod.example.com, and app-test.example.com for test.example.com), the given UI app domain (e.g. https://app-test.example.com) needs to be set to allowedOrigins attribute of the respective organization as described

13
R
GoodData Employee
1 year ago
V
Vasiliy OstrovskyKnown Participant
asked in Metrics and MAQL

Some metrics don't work

What is the error log you’re receiving. Normally in other data sources these metrics should work fine. But with Apache Drill there are some problems with cartesian (cross joins), have you set planner.enable_nljoin_for_scalar_only=false. Since Apache drill is not a stable product, some of the generated SQL’s don’t work with it. If you send me the error log, we can troubleshoot it better. Thanks

7
U
GoodData Employee
2 years ago
V
Vasiliy OstrovskyKnown Participant
asked in Metrics and MAQL

Some metrics don't work

Hi Vasiliy,Are the below parts working when alone used?SELECT COUNT({attribute/dshb_recruiting_ratio.job_posting_candidate_id}) WHERE {label/dshb_recruiting_ratio.application_status} = "Hired" (Metric1)SELECT COUNT({attribute/dshb_recruiting_ratio.job_posting_candidate_id})If they're working when used alone, then maybe it could be due to empty rows being selected in cross joins, i would try to check if below is workingSELECT COUNT({attribute/dshb_recruiting_ratio.job_posting_candidate_id}) WHERE {label/dshb_recruiting_ratio.application_status} IN ("Hired", "Not Hired") (Metric2)Then try to get ratio of SELECT (Metric1/Metric2)And also what is the error you're receiving in console? This could help us to check if it is related to Apache Drill. Thank you,Ulku

7
U
GoodData Employee
2 years ago
V
Vasiliy OstrovskyKnown Participant
asked in Metrics and MAQL

Some metrics don't work

Hi Vasiliy/Yuriy,It is true that in certain circumstances, SQL containing CROSS JOIN (cartesian join) is generated from MAQL statements. We would suggest two way to overcome this error:do what the error message suggests, and set planner.enable_nljoin_for_scalar_only=false on Drill data source. use only such reports which do not generate CROSS JOINs. While it is not entirely straightforward to explain when that happens, basically it's when: the dimensionality is empty (i.e. no attributes in "Rows"), when there are multiple metrics in the report or when one metric contains another nested metric on empty dimensionality (possibly as a result of BY ALL OTHER). So our suggestion would be: try adding attributes in Rows, use metrics in separate reports, and review if possibly BY ALL OTHER can be avoided.Thank you, 

7
U
GoodData Employee
2 years ago
V
Vasiliy OstrovskyKnown Participant
asked in Metrics and MAQL

Some metrics don't work

Hi Vasiliy,Are you receiving the same error for the first MAQL query? The second one seems to be some limitation in Apache Drill related to cartesian join or an inequality join. Are you using Apache Drill as your data source manager?Thank you,

7
U
GoodData Employee
2 years ago
G
Gavin AndereggParticipating Frequently
asked in GoodData.UI

Allow saving of filter setting for embedded dashboards

Hi Gavin,In order to use GoodData dashboards in your application you can either embed them via iframes, or you can built a React application and use GoodData.UI and the react components delivered in it. My colleague Mort has explained you how to set filter context in an application which uses embedding dashboards via iframes. Via setFilterContext command send to embedded dashboard you can set any filter context. See below pictureFor example above when you click Filter button above setFilterContext is called and the dashboard filter has been updated with department=d11. So this command updates those attribute filters which is in dashboard When you embed a dashboard via iframe and display it, you’re in view mode, in order for the user to create filters in it you need to put it to edit mode, via sending command switchToEdit.  This API would not work in GoodData.UI you need to use there Attribute Filter component as you mentioned in your first message, and use the callback functions to get

10
G
2 years ago
A
Allan TalverNew Participant
asked in Metrics and MAQL

Linking two unrelated datasets in MAQL

Hi Allan,In order to implement your second step conversion in GoodData, which is converting the contract amount to some target (destination) currency, you can create another Target Currency Dataset. Your model will look like something below:Then you can change your metric as below: (You can give Date as current date as you have given previously) because you need to also filter the rate according to your target currency.SELECT SUM(Contract Amount)/( SELECT SUM(Rate) BY Date (CurrencyDate), Currency Id, Target Currency Id ALL OTHER WHERE Date (CurrencyDate)=06/01/2021 )After that, you can create your insight to include the metric above (Contract_amount_in_other_cur)And in a dashboard you can add this insight and in the dashboard filter you can choose the Target Currency which will apply the correct exchange rate to the contract Amount.In my sample "Sum Of Contract Amount" is the original Contract Amount and Contract_amount_in_other_cur is the contract amount in target currency which is c

3
U
GoodData Employee
2 years ago
Welcome to the GoodData Community!Cookie settings