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

Projection Expression parsing bug #1

Closed
darylnwk opened this issue Jul 3, 2018 · 1 comment
Closed

Projection Expression parsing bug #1

darylnwk opened this issue Jul 3, 2018 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@darylnwk
Copy link

darylnwk commented Jul 3, 2018

Hi, I am using Expression Builder to create the Expression for QueryInput. I noticed that Expression Builder Projection delimits with comma and space, eg. "#1, #2".

As a result, when there is more than 1 projection, the output is incorrect.

Below is an example of QueryOutput.Items
[ { " #2": { "B": null, "BOOL": null, "BS": null, "L": null, "M": null, "N": null, "NS": null, "NULL": null, "S": "0f3028a2-ee87-447e-9a7a-ee2d94798934", "SS": null }, "ID": { "B": null, "BOOL": null, "BS": null, "L": null, "M": null, "N": null, "NS": null, "NULL": null, "S": "9bbef19476623ca56c17da75fd57734dbf82530686043a6e491c6d71befe8f6e", "SS": null } } ]

The value of expr.Names() is { "#0": "RepoID", "#1": "ID", "#2": "TokenID" }
The value of expr.Projection() is #1, #2

The same Expression Builder works without DAX.

Edit: A workaround I am currently using is to specify ProjectionExpression without using Expression Builder

@anandsas anandsas self-assigned this Jul 3, 2018
@anandsas anandsas added the bug Something isn't working label Jul 3, 2018
@anandsas
Copy link
Contributor

anandsas commented Jul 3, 2018

This will be fixed in the next release

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants