Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Master Item Preview Page doesn't display correctly on May 2022 Patch 4 #26

Open
maxwellginqo opened this issue Sep 2, 2022 · 4 comments

Comments

@maxwellginqo
Copy link
Collaborator

@rikiginqo

The master item preview page is not displaying correctly on the May 2022 release of Qlik Sense.
Please see attached image. Can you please make a fix to resolve this problem?

image_2022_09_02T21_30_49_795Z

@rikiginqo
Copy link
Contributor

@maxwellginqo

I think this issue is caused by the measure expression.
Are you using Excel for the config file? Could you share it with me?

Thanks.

@maxwellginqo
Copy link
Collaborator Author

@rikiginqo
I don't this this is an excel issue. It looks to be a display issue Each row under Measure Name should display a preview for each Measure (or dimension) - but it looks like the preview is floating outside the box.

Let me know if you want to chat about this one.

@sloboy
Copy link

sloboy commented Sep 12, 2022

I had this issue several times when loading measures on a earlier version of QS, but this version of ginqo. I cant recall the specific fix, but I was missing an ID or missing some of the new formatting columns in my excel file. It also may have been an unicode character lurking in the row too. I have had all of these things prevent it from working. This version of ginqo seems to be more finicky about information needing a ' (apostrophe) in excel to keep them as string too.

To test if it is the server or the excel file, try loading the template file in the download. Also, try removing rows in the excel file until it runs. From my experience, the issues have been hiding in my excel file.

@maxwellginqo
Copy link
Collaborator Author

Hey @sloboy thanks for adding your comments to this...

It sounds like you might be right about a recent addition of new formatting columns being the cause...
We'll take a look and update this thread if we make any changes.

Regards,
Maxwell.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants