I'm seeing an error on an insight that was working yesterday: Error trace ID: 11f858ba0c29d988ca269589ae79faed

Hello Steve, the error strictly in the log is a bit vague: "Cannot resolve any join graph" Can you please confirm if any changes had been made prior? Possibly something to the LDM or to Data filters involved?

Not since last night. I'm working around it because I'm using something different, but just curious what caused it.

I guess we would need to access the vis itself and see what is going on there. If you need further help could you please provide a link to the vis in question?

Right away, it looks like there is some issue with the attribute, "task name" ..... checking further

Interesting, is there anyway to view that an attribute has a sortcolumn in the LDM? Its not really obvious

It was a one off issue. There shouldn't be an issue with sorting at all anymore, but you would look for this in the viz itself where sorting is applied.

yeah... but it doesn't tell you its there. Unless I'm not following what you mean

Hi Steve, to check what label has been used to sort any given attribute, you have to go to the LDM as highlighted in the attached screenshot. I am also linking the relevant documentation for your reference: https://www.gooddata.com/docs/cloud/model-data/evolve-your-model/manage-labels/#sort-labels. Let us know if you have any more questions or concerns.

@Moises Morales this is not accurate:

Thank you for the details, Steve. By any chance was the label created manually or via the API? It may be the case that something changed in between releases as to how the setting shows up, but I will take a deeper look.

@Moises Morales we used the UI to set this probably a year and half ago give or take.

I can confirm that the behavior has changed , the icon indicating a custom sort label is defined no longer appears in the LDM, as shown in the documentation. I’ve reported this to our developers, but please note that at this time, I’m unable to provide an ETA for a potential fix if this behavior is not intended. In the meantime, aside from checking the “Sort by” dropdown as you mentioned, you can also verify which label is being used for sorting via the LDM layout endpoint:

/api/v1/layout/workspaces/{workspace_ID}/logicalModel

For example:

"sortColumn": "customer.region_name.sort",
            "sortDirection": "ASC",
            "sourceColumn": "customer.region_name",
            "sourceColumnDataType": "STRING",
            "tags": [
              "Customer"
            ]

Interesting, the way I found it being an issue was by using the /debug on the visualizationobject and looking at the query. Then everything made sense after I found the sort by.

No problem, Steve. We will keep you posted with any details as soon as they become available.

The impact is mostly confusion/issues when trying to work on or leverage LDM features. So it isn't critical, but feels like something that was missed as the UI has evolved and becomes an issue as we try to expand our analytical model build out.

Hi Steve Allow me to jump in while my colleague is out of office. Thank you for sharing more information on the impact this issue. We’ve passed it along to our developers and will update you as soon as we have more details or a fix. We appreciate your patience in the meantime.