PowerBI: credentials failing on OData connection despite successful XML view of OData Generic Inquiries
Hello all,Looking for some OData insight here. The goal: pull a Generic Inquiry through to Power BI.I have the XML page working great with the "Odata" test URL following the naming convention: http://<application site domain>/odata/<company name>I assumed that was the “test” that would ensure that I’d be able to connect to an OData endpoint within an Acumatica instance.However, when I attempt to "Get Data" through Power BI and load in the URL with basic authentication, I have tantalizing visibility to the Inquiries, including the one I want to use, but I'm unable to get past the authentication step in order to finish loading data from the data source.Perplexingly I can't seem to use my regular credentials using Basic authentication, at any level. Here’s the XML. This loads after prompting for Acumatica credentials. However, when I use the same URL and enter the same credentials into “Basic” authentication I’m getting the credentials error: From looking online, I’m curious
I’ve been asked to bring in some historical/static data from a legacy system for a new Acumatica customer. Going to be using it for reference only via GIs I figure if needed. Some of it is quite detailed, many fields, etc. I was going to create and load new Acumatica tables to hold the data and then I realized to use the import scenarios I need a screen name. For my purposes, I don’t' need a screen necessarily. Is there anyway in Acumatica to load data directly into a table from a file, the files at the moment are given to me as tab delimited text files, without having a screen in Acumatica? I’m not a SQL expert, but I’m presuming the tables could be loaded directly via SQL commands, but wondering if I’m missing something..
Hello all,I’ve been following the help guides but am getting errors when I try to schedule an ARM report by email.Looks like when I go to check the status, the execution result is “The report with name Key Financial Numbers is not found” as you can see here: I’m not sure where to more clearly define the report name as the Screen ID is defined in a condition of the Automation Schedule:I initially created this by:navigating to the report itself; defining the parameters & the Print & Email settings; saving those as a report template; and then choosing “schedule template.”As far as I can tell, that is by the book.What am I missing in my configuration? This doesn’t seem to be common so I assume I’ve missed a data element.Thank you all for the ideas!Arline
Login to the community
Social LoginLogin with your Acumatica account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.