Skip to main content
主题#Tableau APIs & Embedding

#Tableau APIs & Embedding17 人正在讨论

提问...
Tableau Community Forums Member (Inactive) (Salesforce 的 Member of the Tableau Community Forums)
2025年10月9日 04:45
Has anyone tried connecting a UAE gratuity calculator API to Tableau?

Hi everyone

I was exploring how to use Tableau for HR and payroll analytics, especially for UAE-based businesses.

I came across a UAE gratuity computation API that calculates end-of-service benefits based on salary and years of service.

Now I’m curious has anyone here tried connecting such external APIs (like HR or financial calculators) directly into Tableau dashboards?

I’m thinking about using it for visualizing total gratuity liability per department or employee group, but I’m not sure what’s the best way Web Data Connector or Tableau Prep script?

Would love to know how others here have handled API-based data visualization in Tableau .

4 个回答
  1. Teckjb Wala
    9月9日 13:24

    Yes, this should be possible. The best approach depends on how often you need the gratuity data refreshed and whether the API supports the authentication method Tableau requires.

    For a relatively small amount of data, you could retrieve the API response and transform the JSON into a Tableau-friendly format before loading it into the dashboard. Tableau Prep can be useful if you need to clean, structure, or combine the API data with employee or department information.

    For recurring HR reporting, I would recommend keeping the API data in an intermediate database or structured data layer and letting Tableau connect to that source. This makes scheduled refreshes, auditing, and historical comparisons much easier.

    You could then use Tableau to analyze total gratuity liability by department, employee group, tenure, or salary range.

撰写回答...
0/9000
Tony Long (FLSC 的 Owner) 提问于 #Salesforce Developer
8月25日 09:54
Webhook response timeout and queue handling for Salesforce CRM REST API syncs

Hello Salesforce Developer Community,

We are optimizing background listener stability and webhook handling when syncing lead payloads into Salesforce CRM endpoints.

Technical Setup:

  • Our integration layer at Frontline Sales Consultancy (flsc.co.uk) triggers automated sales notifications and syncs inbound lead pipelines via Salesforce REST Webhooks.
  • Listener sockets are configured using TLS 1.3 encryption over secure HTTPS.

The Issue:

  1. Under high concurrent transaction spikes, external POST webhook listeners occasionally hit HTTP 504 gateway timeout thresholds before acknowledging payload completion.
  2. Direct REST API calls to the org endpoints resolve normally under 150ms.
  3. Are there recommended Apex asynchronous queueable job patterns or buffer queue settings to optimize inbound payload ingestion without dropping connection sockets?

Any advice on managing high-volume asynchronous API triggers would be appreciated!

Thanks!  

 

#Salesforce Developer  #Tableau APIs & Embedding  #Integration

1 个回答
  1. Kundan Kumar Jha (Infosys)
    8月26日 17:03

    Hey Tony, 

     

    The core fix here is architectural: your Apex REST endpoint should do almost nothing synchronously. Right now, if your handler is doing lead validation, dedup logic, or DML inline before returning a response, that's what's blowing past the 504 threshold under load, real business logic execution easily drifts past 2-3 seconds, which the gateway treats as a dropped connection. 

     

    Recommended pattern: 

    1. Inbound Apex REST method only: validates the payload/signature, publishes a Platform Event with the raw data, and returns HTTP 200 immediately. Nothing else happens in that thread. 

    2. A separate Platform Event trigger picks up the event asynchronously, does your actual business validation, then enqueues a Queueable job (implementing Queueable, Database.AllowsCallouts if you need outbound calls) to do the real processing/DML. 

    3. Cap callouts below Salesforce's 100-per-transaction limit, chain overflow records to a new Queueable automatically rather than dropping them. 

    4. If Apex's async queue itself hits a capacity rejection under heavy concurrent load, catch that exception and fall back to a Scheduled job (e.g., retry in ~20 seconds) so nothing gets silently dropped. 

     

    This decouples network response time from your actual processing time entirely, so gateway timeouts stop being a factor regardless of how complex the downstream logic is. Your observation that direct REST calls resolve under 150ms but webhooks spike under concurrency confirms it's specifically the synchronous processing inside the handler causing the bottleneck, not the API layer itself. 

     

    Also worth adding: idempotency (dedupe on a unique payload ID) since Platform Events and async retries can occasionally redeliver, and Named Credentials for any outbound calls so secrets stay out of code.

撰写回答...
0/9000
Tableau Community Forums Member (Inactive) (Salesforce 的 Member of the Tableau Community Forums)
2025年7月8日 13:18
Any suggestions or articles would be highly appreciated. Best,
5 个回答
  1. Rajneesh Sharma
    8月25日 09:51

    Hi Raju, 

      

     Recently we have built a Tableau Dashboard Extension that adds a chat panel right inside the dashboard — so instead of eyeballing charts, users can just ask questions in plain English ("what drove the drop in Q2 expenses?", "compare loan fees to expense spend") and get grounded, numeric answers. 

    How it works: 

    • One lightweight local/hosted backend serves multiple dashboards at once — the model automatically figures out which dataset(s) a question is about, and can even blend two datasets in one answer.
    • Every answer is computed by the LLM writing read-only SQL against a real snapshot database (using Tableau's own Hyper engine) — not hallucinated numbers, not a live query against the workbook. This keeps answers fast, accurate, and safe even on 10M+ row extracts.
    • Each dataset ships with auto-generated reference docs (a description + data glossary) so the model understands field meanings, grain, and caveats before answering.
    • An admin flow can onboard a brand-new Tableau Cloud workbook automatically: pull it via the REST API, extract the embedded data, and have the LLM draft the descriptive docs itself.
    • Row-level-security workbooks are auto-detected and blocked from onboarding unless explicitly overridden, so a shared snapshot never leaks restricted rows.

    Please upvote this response if this will be helpful to you. 

     

    Regards 

    Rajneesh

撰写回答...
0/9000
raju Prasad
2025年7月8日 13:18
Any suggestions or articles would be highly appreciated. Best,
1 个回答
撰写回答...
0/9000
Nate Laning
8月4日 16:28
Is it possible to replace passwords using Tableau REST API?

I have roughly 120 data sources that use a connector to link directly to my data warehouse. I'm changing the password for the user that is used with this connector, but I'm trying to find an alternative to opening each data source in the Tableau Cloud IT, update the password, and republish. Is there any way to do this with the Tableau REST API? If so, how? 

 

#Tableau APIs & Embedding

5 个回答
  1. Ankit Vashishth (Growth Natives)
    8月5日 11:05

    Hi @Nate Laning Yes, but not by directly updating the embedded password through the Tableau REST API. The recommended approach is to use the Update Data Source Connection REST API endpoint to update the connection credentials for each published data source. You can automate this by writing a script that authenticates to Tableau Cloud, retrieves the list of data sources, and updates the username and password for each connection. If all data sources use the same credentials, this is much faster than manually republishing every data source.

撰写回答...
0/9000
Umesh Chorge 提问于 #Tableau Server
6月11日 08:05
Tableau Web Edit Republish – Athena Credentials Not Retained, Extract Failing

I updated the Athena DB connection credentials (username/password) in a Tableau workbook, and the extract refresh was working successfully after the update.

After around 5 days, I performed a web edit on the dashboard and made some changes. During this process:

  • Tableau did not prompt for credentials
  • While republishing, only the “Embed credentials” option was available

However, after republishing the workbook, the scheduled extract job started failing with an incorrect username/password error.

This is confusing because the credentials were already updated earlier and were working fine before the web edit.

 

My queries:

  • Why is Tableau not asking for credentials during web edit or republish?
  • Does web edit/republish overwrite or remove previously saved credentials?
  • Why would the extract fail with incorrect credentials even though they were updated earlier?
  • Is there any known limitation or behavior with Athena connections in such scenarios?
  • does role affect?

#Tableau Server  #Tableau Public  #Tableau Desktop & Web Authoring  #Tableau Cloud  #Tableau  #Tableau APIs & Embedding  #Tableau Community Updates

8 个回答
  1. Emeric LE SAULNIER DE SAINT JOUAN (M2)
    6月12日 07:25

    Hi @Umesh Chorge

     

    dealing with WebEditing and credentials can be a bit unstable. I've seen a lot of instances over the years were credentials for some mysterious reasons were not committed or using old ones or using credentials from another tenants while the Analysts were working daily on multiples tenants.  

    This is one example: 

    https://help.salesforce.com/s/issue?id=a02Ka00000lYbc8IAC

     

    As you seem to work with embedded data source directly in the workbook, as Diego said in his earlier post, use published data sources. To keep your datasource stable and modify your workbook content irrelevant of Athena connections even in WebEdit. 

    And ideally you modify your published data sources using Tableau Desktop if you can.

撰写回答...
0/9000
Umesh Chorge 提问于 #Tableau Desktop & Web Authoring
6月17日 11:16
Feasibility of Conditional Dashboard Refresh Based on Data Availability (Success File)

Our requirement is:

  • The dashboard (or extract) should refresh only when the latest data for the same day is available at backend DB (for example, based on the presence of a success file or updated data in the source).
  • If the updated new data is not yet available, the refresh should not RUN but instead wait and retry in the next cycle.

We would like to understand:

  1. Is it possible in Tableau Server to trigger refreshes based on a success file or data availability check?
  2. What are the recommended approaches to avoid unnecessary refresh failures when the source data is delayed?
  3. Any guidance, best practices, or implementation examples would be highly appreciated.

#Tableau Desktop & Web Authoring  #Tableau Public  #Tableau Server  #Tableau Cloud  #Tableau  #Tableau APIs & Embedding

5 个回答
  1. Don Wise (Tableau Community Ambassador)
    7月23日 15:09

    This latest response is unfortunately a ChatGPT post. Based on the number of responses overnight and through today, the effort might even be automated. We have a BAN on any A.I. posts due to the high error rate.  So, we're considering these posts as spam. Apologies for any inconvenience this may have caused.

撰写回答...
0/9000
Mukesh Mathur
7月16日 06:32
It is possible to Save the DB Connection or Password into Tableau Desktop or Prep ?

Hi, 

When i am developing the Tableau App or Get the data form Different Data Base firttime i connect and enter our credentials  and after that we save the application in my local System or Server System. But when i am opening or any chnage required in our dashboard Tableau need credential every time . It is not good or not manageble. Please give the permanent soultion because of In Qlik Sense ,Power BI they no need to many times input they enter first time and save in its repository. 

 

 

 

#Tableau APIs & Embedding

3 个回答
  1. Deepak Rai
    7月16日 18:11

    Apart from what Diego Detailed,  Tableau Desktop can also save credentials in many scenarios. For supported database connectors, selecting "Embed Password" (or "Save Password") allows the workbook to reconnect without prompting every time. 

撰写回答...
0/9000
Mukesh Mathur
7月16日 06:21
Can we Get the data from S4/HANa REport or Tcode data into Tableau.

Hi , 

I have a SAP Access and when i am start sap pass the Tcode of REport and pass the some parameter like Unit,Month and Type of Employee report show the Monthly Attendence or other required data. Can It is possible to Fetch the Tcode or Pass the PRogram Name and give the entire result into Table. 

 

#Tableau APIs & Embedding

1 个回答
  1. Saurabh Kumar (Cloud Matrix Consulting Pvt Ltd)
    7月16日 12:59

    Hi @Mukesh Mathur

     

    Yes, it's possible, but Tableau doesn't typically execute SAP T-Codes directly. A common approach is to expose the underlying data through

    SAP HANA views, CDS views, BW queries, or OData/BAPI services, and then connect Tableau to those sources. If the report is generated by a custom ABAP program, your SAP team may need to expose the report data through a supported interface before Tableau can consume it.

撰写回答...
0/9000
Martina De Luca
6月16日 19:24
PowerPoint Integration

Hi all, 

 

I'm using the new Microsoft add-in to show Pulse Metrics images into PowerPoint slides. I'm able to insert and update the images, but as soon as I add a non-Tableau image to the presentation it stops working as expected. I'm able to add new images, but not refresh the data. The following error message appears on the refresh section: "Error looking for Tableau generated images within the presentation".  

 

I've tested the same in Word and it's not an issue there. 

 

Any suggestions on how to keep the refresh functionality while including other images?  

 

Thanks! 

 

#Tableau APIs & Embedding

1 个回答
  1. Deepak Rai
    7月9日 13:32

     I'd recommend opening a Tableau Support case and sharing a sample presentation along with the add-in version and Microsoft 365 build. 

撰写回答...
0/9000