I trying to import tally data to Power BI using ODBC. I have create multiple accounts in tally ERP9. This data connected in ODBC data source 64bit. After that connection, I am trying to access this data in power bi using Get data option. But I have not access any tally data. Here shows error is "ODBC: An error occurred but no ODBC error information was available.".
I am followed below steps-
1.Install Power BI Desktop application, Tally ERP 9.0.
2.Create Ledger accounts in Tally.
3.Connect tally data to ODBC data source 64bit.
4.Go to power bi Desktop application. Click on "Get Data" option.
5.Choose ODBC option, click on tally_9000 and enter credentials of database. After entering credentials click on "Connect" button.
But I have not access any tally data. Here shows error is "ODBC: An error occurred but no ODBC error information was available.". Also, I am trying it in Excel but shows same error there.
Related
Is there a way to connect to power bi services workspace/dataset via excel power query?
Excel can connect via Get Data>>>From Power platform but is there a way to connect via excel power query?
There is a power platform section in power query but not to the power bi platform, is there an add-in or driver that can be installed to make the connection available?
There is an old process that connects to an azure DB which needs to be replaced and hoping to find a way to connect to PBI dataset rather than rebuild the whole process?
If the Power BI is published to the service, use Data > Get Data > From Power Platform > From Power BI.
You cannot use Power Query to get data from published Power BI datasets.
You can connect to the dataset, or you need an entry point further upstream, such as in a dataflow, to connect to the tabular data for further processing in Power Query.
My Team is working with Power BI, where we use a Report Server and the Cloud. For one Power Bi file, we connected some Excel Sheets and a Access File. Everything is fine. The upload on every Server is working. Nonetheless, if we try to refresh the Power BI file there is a certain error.
If we try to refresh the PowerBI File in the report server the error is:
SessionID : a63570ad-2411-4b53-b9ce-6a969cb00c97
[0] -1055784932 : DataFormat.Error: Unspecified error. Project_Acquisition_Overview_AE-BE_current.accdb. ;Unspecified error. The exception was raised by the IDbCommand interface.
[1] -1055129594 : The current operation was cancelled because another operation in the transaction failed.
[2] -1055784932 : The command has been canceled.. The exception was raised by the IDbCommand interface.
If we try to refresh the PowerBi file via the Cloud the error is following:
Fehler bei der Datenquelle{"error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","pbi.error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","parameters":{},"details":[{"code":"DM_ErrorDetailNameCode_UnderlyingErrorCode","detail":{"type":1,"value":"-2147467259"}},{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"Microsoft Access: The 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine. The 64-bit version of the Access Database Engine OLEDB provider may be required to read 'Project_Acquisition_Overview_AE-BE_current.accdb'. To download the client software, visit the following site: https://go.microsoft.com/fwlink/?LinkID=285987."}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.ValueError.Reason","detail":{"type":1,"value":"DataSource.NotFound"}}],"exceptionCulprit":1}}} Table: Acquisition_Overview.
Cluster-URIWABI-NORTH-EUROPE-L-PRIMARY-redirect.analysis.windows.net
Aktivitäts-IDb5924bb8-a673-4ebd-8dc5-94d8d4af6b02
Anforderungs-IDd4f1083a-dfd5-3c96-dfca-4ecca3a57eb1
Zeit2021-11-18 10:03:07Z
Does someone have an idea what could be the problem?
The following on-premise data sources can NOT be used with Power BI Cloud
SAP BW
SAP HANA
ODBC
Access DB / Legacy Excel files (.xls)
This means that Access DB cannot be refreshed in the Power BI Cloud.
I want to provide access to data from a DataWareHouse to several users of my company. I need to create a dataset with filtered data and then I want to provide to granted users access to those data inside Excel on Mac Os.
I don't know if this is possible as the feature "Analyze on Excel" is not available for download on Mac Os.
Any ideas?
Connection to the Power BI datasets via Power Query, can't be done on Excel for MacOS as it is not supported. Power Query for MacOS Excel is limited to csv, json and d few others. Power Pivot for MacOS isn't available.
You can connect to OLAP sources like SQL Server Tabular using this paid for option, but only for On-premise SSAS, or Azure Analysis Service. If you have Power BI Premium, the CDATA plugin might be able to connect to the xmla endpoint of the dataset.
The other option is create the filtered data model with PBI Desktop on Windows and deploy it to the service, then to give them access to the Power BI Service. The user can then create their own reports, or export the data via csv, but the export size it limited to 100,000 rows.
For Mac users Power BI is mostly limited to viewing/creating the reports in the service.
I have a BigQuery instance and I have shared a view with a service account. This service account has the "bigQuery.User" role. I setup Simba ODBC drivers on my Ubuntu machine, installed Libreoffice base on it and also modified the odbc.ini file to use the above service account. I'm able to connect to Bigquery but when I try to query the shared view, it throws an error saying that "user does not have BigQuery.tables.create permission for table ...". Looks like LibreOfficeBase Base is trying to create some temp tables. Tried with MS Excel and same error is thrown
My questions:
Isn't the "bigQuery.User" role enough to query data from shared datasets/tables?
Why does Libre Office Base require such extra permissions?
What I tried:
I shared the data with a user account(someuser#gmail.com). I gave the same role i.e. bigQuery.user to this account. I was able to query data successfully from this account.
I also tried on Tableau. Tableau has native support for Bigqyuery and also supports ODBC connections(to connect BigQuery, MySql, etc). I tried with both i.e. connecting to Bigquery using Tableau native BigQuery support and using ODBC connection. It worked with native BigQuery but not with ODBC connection(maybe it has the same issue as LibreOffice base and MS Excel)
I have power bi configured on Azure, a dataset reading its data from excel document which is updated on daily basis.
The refresh is done manually through powerbi desktop. After I click on refresh, my reports and dashboards are reading updated figures, I open it from power bi desktop; however if I open it from any browser, data is not updated, I will have to publish my power bi reports and dashboards from power bi desktop publish button in order to see my data updated from browser.
Power BI desktop is the development tool for powerbi.com, after you have published it to powerbi.com, it has no relation with your offline .pbix file. Publishing it again (with the same name), will overwrite the file with it's data.
So a local refresh in power bi desktop has no influence on the file in powerbi.com
If you want that powerbi.com can read data from your excel file (on Premise), you'll have to setup a powerbi gateway. More information on following link:
Power BI gateway personal mode
On-premises data sources
A personal gateway is required in order to refresh datasets that get data from a supported on-premises data source in your organization.
With a gateway, REFRESH NOW and SCHEDULE REFRESH are supported for datasets uploaded from:
Microsoft Excel 2013 (or later) workbooks where Power Query or Power Pivot is used to connect to and query data from a supported on-premises data source. All on-premises data sources shown in Get External Data in Power Query or Power Pivot support refresh except for Hadoop file (HDFS) and Microsoft Exchange.
I had to uninstall my "on-premises data gateway (personal mode) and reinstall updated version. it is working now.