Ask questions, get answers and engage with your peers
Start discussions, ask questions, get answers
The latest CData product news and updates
Explore and RSVP for upcoming events
Guides, documentation and support articles
Share product questions and get support
Join a group and share common interests
🗓 Event Dates: September 22-29, 2023📍 Location: Right here in this threaded discussion on the CData Community Site👥 Experts on Deck: Jerod Johnson, Riley James, Jon Tye, and rock stars from the CData Champions Program 👋 Hello CData Community,The day we've all been waiting for is finally here! Welcome to our exclusive Ask Me Anything (AMA) session focused on Workday and its integrations with CData. Why You Should Participate:Get expert insights from Jerod Johnson, Riley James, Jon Tye, and other rock stars from our CData Champions Program. Learn best practices for integrating Workday with CData. Discover tips and tricks to optimize your Workday experience.How to Participate:Ask Away: Use this thread to post your questions about Workday and CData integrations. Share Your Knowledge: If you have tips or experiences to share, we'd love to hear them! Engage: Feel free to comment on other community members' questions and answers. To get the ball rolling, here are some questions for the ex
SAS Studio environment can use any JDBC data source thanks to its JDBC interface. On previous issues we have monitored a certain query modification done by the tool or the SAS/ACCESS interface resulting in badly formatted queries, throwing both server and driver errors. On these occasions using the following code to connect and query enables a ‘’passthrough mode” which preserves the query from any modification done by SAS platform. Example: proc sql; CONNECT TO JDBC as conn (classpath="/Public/Drivers/cdata.jdbc.databricks.jar" class="cdata.jdbc.databricks.DatabricksDriver" schema=<databricks_schema> URL="jdbc:Databricks:Server=<your_server>; HTTPPath=<yourhttppath>; AuthScheme=PersonalAccessToken;Token=<your_token>"); Select * from connection to conn (Create table test1 (Name Varchar(10))); disconnect from conn; quit; Additional details can be found on the following documentation: SAS Help Center: SQL Pass-Through Facility Specifics for JDBC
When publishing a Workbook on Tableau Server, the necessity to configure User and Password properties may arise. In case when using the cdata.excel.legacy.taco file in the "C:\ProgramData\Tableau\Tableau Server\data\tabsvc\vizqlserver\Connectors" directory, the following window will appear in the Tableau Server interface: The User and Password properties need to be configured for successful data retrieval. However, even when these values are set in their respective fields (Username and Password), the driver fails to return the data. To ensure proper functionality, these properties must be set in the Connection String field. However, this approach introduces a security concern, as the Password remains unmasked. This means that any user with access to the published Workbook can potentially view the exposed Password. To address this issue, you should take the following steps: Remove the "legacy.taco" file from the directory located at "C:\ProgramData\Tableau\Tableau Server\data\
Hi,Following the instructions on the help I have set the property “SSLServerCert” to “*” to allow all certificates. If not specified, any certificate trusted by the machine is accepted.Use '*' to signify to accept all certificates. Note that this is not recommended due to security concerns. I do get authorized on the Zoho CRM server. However on connector side of the CData component I get the error message as shown on the last image below. Error Message
In order to enable Connect Server to communicate with the Facebook API during the sign-in process, the authorization server (OAuth) will redirect the user to the Connect Server redirect URL, which by default is: https://oauth.cdata.com/oauth/. This URL must correspond to the callback URL specified in the application configuration, as illustrated in the accompanying screenshot. You will have the option to enter this value in the Meta for Developers section of your Facebook login -> Settings page.
CData provides comprehensive connectivity to your Workday data. If you're just getting started, you can read our Knowledge Base article on connecting to the robust Workday Query Language (WQL) and Reports-as-a-Service (RaaS) APIs available for Workday. This article serves as a guide for making the most of your CData & Workday integration once you've enabled the required services. The practices outlined below come from collaboration between CData's and Workday's engineering teams and are designed to help reduce the load on your Workday instance, reduce the load and cost on your own systems, and facilitate more efficient analysis and reporting on your Workday data. Using the Workday Prism Data Catalog Our top recommendation is for users to create tables and datasets in the Data Catalog (in Prism Analytics) whenever possible. Workday Prism Analytics acts as a data hub built into Workday, making Workday easier to analyze and report on without compromising the security and fidelity of
Finally! Connect to Workday data in your favorite data tools With the Workday Rising event kicking off in San Francisco this week, we’re highlighting CData connectivity solutions that help you bring Workday data to enterprise users directly within the tools they know and love. Now, you can finally access, visualize, and analyze Workday data wherever you need to. CData gives your Workday data wings!CData provides a hassle-free way to connect to Workday data from anywhere. You might even say we give your data wings 🕶Learn more Working in Tableau? Get Zero-ETL Integration with WorkdayAccessing Workday reports in any third-party tool is notoriously difficult. Along with our partners at Tableau, we’re changing that. The best part? We’re doing it all without moving your data from Workday.Read more Hear from our customersBJ’s Wholesale Club improves employee retention by over 10% with CDataConnecting Workday to Tableau gave BJ’s the insights to understand and act on HR trends, helping to imp
The error "The message received was unexpected or badly formatted" usually is caused because the server and client might not possess a mutually supported cipher suite. A common way to fix this issue is to use one of CData’s hidden connection properties, which is shared among all our drivers, no matter the edition. In the “Other” connection property, type the following value: UseInternalSecurityAPI=True UseInternalSecurityAPI, when set to TRUE will force the driver to use CData’s internal implementation of SSL, which supports more protocols and cipher routes than some versions of Windows. When the property is switched to TRUE, the driver will be completely independent from Windows' Security API. Please reach out to support@cdata.com if this does not resolve the problem for you.
This error commonly arises during the replication of very large tables, indicating that the table contains more records than the internal mechanism can effectively track. Our REPLICATE command stores extra duplicate checks and Sync keeps a list of primary keys to facilitate these checks. Depending on the size of the tables involved, this side of the replication may overflow, resulting in the above error. To resolve this issue, you can disable duplicate checks by setting the ‘EnableDuplicateProtection’ property to False in the Job Additional Options, as shown in the following screenshots: This will help you bypass the error. Please reach out to support@cdata.com if this does not resolve the problem for you.
The reason why this error is getting thrown is because of the Organization URL. This connection property should start with https:// so the correct format in your case would be https://<organisationName>.crm.dynamics.com. This error then leads to the scope issue which due to your URL, throws an invalid URI form, presented as <organisationName>.crm.dynamics.com/user_impersonation instead of https://<organisationName>.crm.dynamics.com/user_impersonation. To fix this error kindly change the Organization URL connection property value. Please reach out to support@cdata.com if this does not resolve the problem for you.
I have an angular project that is being built with the command: `npm run start`which runs the script: "start": "set NODE_OPTIONS=--openssl-legacy-provider && ng serve --proxy-config proxy.conf.json --prod",When the app is opened in "http://localhost:4200" it seems to load ok, but as soon as I change the user using the command: _setUser(window._user.sally_superAdmin);The user info is returned but I get an error message in the console: main.js:1 ERROR Malformed UTF-8 data rc @ main.js:1 handleError @ main.js:1 next @ main.js:1 __tryOrUnsub @ main.js:1 next @ main.js:1 _next @ main.js:1 next @ main.js:1 next @ main.js:1 emit @ main.js:1 main.js:1 ERROR TypeError: Cannot read properties of undefined (reading 'filter') at a.project (main.js:1:4756133) at a._next (main.js:1:3551188) at a.next (main.js:1:3529941) at a._next (main.js:1:3551286) at a.next (main.js:1:3529941) at h._next (main.js:1:3557774)
Hello Team,Can you are aware for connectors authentication in restricted environment would require URL Whitelisting and for Facebook , I have to “facebook.com” done.Still doesn't work. Am I missing anything,Any quick response would be appreciated.BTW we are working on Facebook, Instagram, LinkedIn and YouTube CDATA Conectors. RegardsNS
Explore e-Books, whitepapers, webinars and more!
Contact our support team and we'll be happy to help you get up and running!
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.