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

[Issue] : Facing issues while importing a table in AAS model using TE3 #1007

Closed
kkmalik89 opened this issue Oct 4, 2023 · 6 comments
Closed
Assignees
Labels
issue: bug Confirmed as a bug in TE3
Milestone

Comments

@kkmalik89
Copy link

kkmalik89 commented Oct 4, 2023

Describe the issue
A clear and concise description of what the issue is.

** Which version are you currently using? **
3.10.1

To Reproduce
Are you connected to SSAS/AAS/Power BI or working offline? - AAS

Steps to reproduce the behavior:

  1. Import the model in TE
  2. Right click on Tables and import tables.
  3. Choose any table/view. It shows 'Update Schema' popup.
  4. See error

image

Expected behavior
Table import successful.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • Windows version: 11

Additional context
Add any other context about the problem here.

@otykier
Copy link
Collaborator

otykier commented Oct 5, 2023

Hi @kkmalik89
Are you connecting to a dedicated synapse SQL pool, by any chance? If so, we are currently aware of an issue in that regard, and will make a fix available with our next update.

As a workaround, enable Use Analysis Services for change detection and import tables by copying existing ones, modifying the M expression, and running a schema update, as described here.

@otykier otykier added the issue: bug Confirmed as a bug in TE3 label Oct 5, 2023
@otykier otykier added this to the 3.12.0 milestone Oct 11, 2023
@otykier
Copy link
Collaborator

otykier commented Nov 28, 2023

Fixed in 3.12.0, thanks for reporting!

@otykier otykier closed this as completed Nov 28, 2023
@kkmalik89
Copy link
Author

Hi @kkmalik89 Are you connecting to a dedicated synapse SQL pool, by any chance? If so, we are currently aware of an issue in that regard, and will make a fix available with our next update.

As a workaround, enable Use Analysis Services for change detection and import tables by copying existing ones, modifying the M expression, and running a schema update, as described here.

Yes, We are connecting to Synapse dedicated SQL pool.

@kkmalik89
Copy link
Author

Fixed in 3.12.0, thanks for reporting!

Thanks. Will download this version.

@kkmalik89
Copy link
Author

It works in version [3.12.0]. Thanks @otykier !!

@otykier
Copy link
Collaborator

otykier commented Nov 28, 2023

Thanks for the confirmation :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
issue: bug Confirmed as a bug in TE3
Development

No branches or pull requests

2 participants