Having an issue with setting the wdf_filter. For s...
# gooddata-cloudd
Doug Creighton
01/08/2025, 9:39 PMHaving an issue with setting the wdf_filter. For some reason it says it does not exist. Can't think what i'm doing wrong. the URL was copy and pasted - same with the bearer id and the tenant workspace exists
j
Joseph Heun
01/09/2025, 8:47 AMHi Doug, it looks like you might be missing the column name in your body. Could you please review the parameters here:
https://www.gooddata.com/docs/cloud/workspaces/workspace-data-filters/#set-up-workspace-data-filters
Please note the section on ColumnName Usage
d
Doug Creighton
01/09/2025, 2:05 PM@Joseph Heun I'm doing the child one. There isn't a column name
This is the URL: https://reporting.laivly.cloud/api/v1/entities/workspaces/tenant-ulta-clone/workspaceDataFilterSettings
j
Joseph Heun
01/09/2025, 2:37 PMHi Doug, I've checked out the workspace and parent workspace and can see that this is the only WDF present. Could you please confirm if this is the filter you are trying to apply to the child workspace, or if you are trying to create a new one?
d
Doug Creighton
01/09/2025, 2:39 PMyes, i'm trying to use this filter on the child space
j
Joseph Heun
01/09/2025, 2:39 PMI think the id may have been set as:
"tenant_tenant-clone-for-testing"
d
Doug Creighton
01/09/2025, 2:40 PMyes, i saw that, not sure how that fits into the problem
Doug Creighton
01/09/2025, 2:40 PMthe child filter doesn't even refer to that id
{
"data": {
"id": "tenant-ulta-clone",
"type": "workspaceDataFilterSetting",
"attributes": {
"filterValues": [
"ulta"
],
"title": "ulta clone"
},
"relationships": {
"workspaceDataFilter": {
"data": {
"id": "wdf__tenant_id",
"type": "workspaceDataFilter"
}
}
}
}
}
Doug Creighton
01/09/2025, 2:41 PMAlso the error says endpoint doesn't exist or i don't have access, it hasn't even got to read the body.
j
Joseph Heun
01/09/2025, 2:58 PMI'm testing the endpoint and it works, and I can see that your user as the necessary access. I'm not seeing authentication errors in the logs based on the traceID. All of this seems fine.
Could you maybe try to reset your postman, and re-authenticate to see if that helps. If not, we can try making the call from the admin user as well and see if it works with that user.
d
Doug Creighton
01/09/2025, 2:59 PMI am an admin user
This is the trace id i'm getting
"traceId": "1d7f3dd7e1e0e991ee3125ef783b31af"
Doug Creighton
01/09/2025, 3:00 PMI tried in python etc... it's giving me the same error
Doug Creighton
01/09/2025, 3:01 PMmaybe I need to create a new bearer id?
j
Joseph Heun
01/09/2025, 3:07 PMaaah, ok. I don't see the workspace with the name tenant ulta clone
Joseph Heun
01/09/2025, 3:07 PMshould it be for "*ulta clone"*
Joseph Heun
01/09/2025, 3:07 PMI think you just need to change the workspace ID in your endpoint
d
Doug Creighton
01/09/2025, 3:34 PM"ulta clone" is the name not the id. I can't put "ulta clone" in the url - there is a space
Doug Creighton
01/09/2025, 3:34 PMthis is the child space
j
Joseph Heun
01/09/2025, 3:56 PMOk, so I really believe the error is misleading here. I'm checking the id of the WDF again, and it is showing as "tenant_tenant-clone-for-testing" but in your body you have sent above, it is showing as "id": "wdf__tenant_id", Could you please try making the call with the id as "tenant_tenant-clone-for-testing"
d
Doug Creighton
01/09/2025, 4:02 PMyes that did it
🙌 1
5 Views