Integrating Tableau with Salesforce: a dashboard is not a write-back

The Monday pipeline meeting opened on a blank screen. On Friday a steering note said Tableau was finished. Tableau Next would replace it, and the numbers now lived in Salesforce because Data Cloud had a new name. Someone archived the workbook the meeting had used for two years. The analyst who published it was told not to refresh the extract. The seller who asks for the figure gets a shrug, then a suggestion that the dashboard should write the number back onto the opportunity. Nobody can show that write. The cited page does not describe it. The figure they needed was a filter on last quarter, maintained by one person, on a product that still has its name. The call for the number did not land. The slide caused it.

That meeting is the integration this page is about. Tableau was acquired in 2019 and kept its name. Tableau Next does not replace Tableau. Tableau is not Data 360. A dashboard shows a cut of data someone chose. It is not an identity resolution. A diagram that does not name the system the workbook reads, the object or extract it shows, and the failure when the number is missing is a poster. The build sits on the Tableau implementation page. The ownership story sits on what happened to Tableau. This page is the number the meeting opens.

#The system

Tableau was acquired in 2019 and kept its name. You still ask for it by that name. A workbook is a set of questions pointed at a source, published by a person, and opened by a meeting. Changing the logo on a slide does not move those questions into an opportunity field. The acquisition changed the owner of the product. It did not, on the facts this page uses, retire the workbook.

Tableau Next does not replace Tableau. Treat any sentence that says it does as a claim you have not been shown. If a partner draws one arrow from the current workbook to Tableau Next and leaves the meeting off the page, they have skipped the thing people open. Next can be a separate conversation, with its own reason and its own owner. It is not the automatic next step of an acquisition that kept the original name. Do not archive a workbook because a slide ran out of boxes.

People mix Tableau into Data 360 because both words appear in the same programmes. The help page this guide cites states a rename. This page quotes it once, and only to say Tableau is not Data 360: "As of October 14, 2025, Data Cloud has been rebranded to Data 360." The sentence does not mention Tableau. It does not say a workbook has become a CRM record. It does not say Tableau Next has taken the meeting. Put 14 October 2025 on the Data 360 line. Leave Tableau on the 2019 line, with the name it kept.

Name the system the workbook reads. A warehouse table, a Salesforce object, or an extract a person refreshes are different systems. "Salesforce" with no object is not a name. "The data platform" is not a name. Write the name the publisher would use when the extract fails on Sunday night. If the workbook reads a spreadsheet a person still edits, say so. That person is part of the system. A design that hides them will discover them on Monday, in the meeting, when the number is wrong.

This page will not invent a connector name, a middleware edition, or a price. The cited sentence does not publish a Tableau licence fee, and it does not publish a path from a dashboard back into a record. If a proposal adds either, ask for the sentence. When they cannot show one, strike the line.

#The object

Name what the workbook is allowed to show. If it reads Salesforce, name the object and the fields. Opportunity with amount, close date, and owner is a different cut from a custom object nobody reports on. If it reads an extract, name the extract and the person who publishes it. The object of the integration is that named cut. "The dashboard" is the picture. It is not the object.

A dashboard is not an identity resolution. It does not decide which customer is the real customer. It does not merge two contacts. It does not pick a surviving phone number. A filter on a region is a cut someone chose for a meeting. If the programme needs a decision about which profile is which, that decision belongs on a different page, with a different owner. Do not brief the workbook as that decision. You will archive a chart and still have two contacts.

Do not invent a write-back. A seller looking at a bar is not writing the opportunity. A click in a dashboard is not, on this page, an update to a record. The cited sentence does not describe that path. A partner who adds "the chart updates the CRM" has invented a second integration and given it no failure. If you truly need a person to change a record, they change it in Salesforce, under the permissions they already have. The workbook stays a view.

Write who may see the cut. A workbook that reads a warehouse does not inherit field rules from the org just because both carry the Salesforce name. Say which sellers may open which workbook. Test it as that seller. A view that includes the whole organisation because a project sandbox was loose is a design. It may be the wrong one. Write it down before the meeting invites a guest.

The publisher is part of the object. A workbook with no named publisher is already failing, even while the picture still loads. Write "no publisher" on the line if that is the truth. Do not hire a firm to guess. The next person who can refresh the extract is the integration, as much as any line on a diagram.

#The failure when the number does not land

The call does not land when the meeting opens and the number is missing, late, or silently stale. The extract failed on Sunday. The source moved a column. The publisher is on leave and nobody else may refresh. Someone archived the workbook because a slide said Tableau Next had replaced it. Each of those is a different failure. Write the one this meeting will actually meet: the pipeline figure is not on the screen, and here is who is told.

Say what the meeting does in that hour. They may use last week's number and say so. They may stop the forecast. They may not type a guessed figure into the opportunity and treat the guess as the integration. A handwritten number is a human edit. It is not a write-back you forgot to draw. If the room starts typing, you have left the integration and started a data fix with no owner.

Do not describe the blank screen as an identity problem. A missing bar is not two profiles that failed to match. Do not describe it as Data 360 being down, unless Data 360 is the named source and you have a separate sentence for it. The usual failure is simpler. The workbook's source did not answer, or a person switched the workbook off.

Tableau Next does not fill that gap by existing. If Next is not in the room, with a publisher and a question the meeting has agreed to open, it is not the fallback. Saying the new product will show the number is a poster. The failure still needs a person and a last-known figure.

This page states no price for the blank hour, and no promise that the picture is current. Currency is a choice about the source. Write whether a late extract is acceptable. A partner who promises the dashboard will always match the record, without naming the source, is selling a wish.

#A diagram that omits three names is a poster

A diagram that does not name the system, the object, and the failure is a poster. A cloud, the Tableau logo, and an arrow into Salesforce do not make a design. Draw three labels. The system the workbook reads. The object or extract it shows. What the meeting does when the number does not land, including the publisher's name.

Do not draw a write-back arrow to make the poster look like an integration. The arrow is an invention. Leave it off. If a later project adds a real write, that project names the field, the user, and the failure when the write hits the wrong record. It is not this page, and it is not implied by 2019.

Do not put Tableau and Data 360 in one box. The quoted sentence exists so you can say they are not the same product. A box that says both has used a rename as a migration. If Data 360 is genuinely the source, label it as the source, name the data set, and keep Tableau as the workbook that reads a cut. Two labels. Two owners. If you cannot write both sentences, you have one picture wearing two logos.

Cross out systems the workbook does not read. An estate diagram with every database in the company is a poster about the company, not an integration. The meeting uses one workbook. Start there.

#What you settle before anyone archives a workbook

Write five lines before anyone switches a workbook off. The meeting that opens it. The question it answers. The system it reads. The person who may publish. What that meeting does when the number is missing.

Then say what you are not buying. You are not buying a replacement called Tableau Next unless that product is in the room with its own question. You are not buying a write-back. You are not buying identity resolution under a chart. You are not buying a Data 360 migration because of a rename. You are not buying a price this page does not state. This page does not give Tableau an end date. The 2019 acquisition was not a shutdown.

The implementation page is where the inventory of workbooks, the overlap week, and the buyer test are taken apart. What happened to Tableau is where 2019, the name, and the refusal to invent a purchase price are kept. Use those pages when the meeting starts arguing about the acquisition. Bring the meeting back to the blank screen.

Agree who may archive a workbook. A single analyst on a Friday is not a cutover. The meeting has to agree the new place is the place they will open. Until they do, leave the extract on.

#A test the meeting can run

Open the workbook as the seller who uses it. Confirm the number matches the question you wrote down, not a neighbouring question that looks similar. Confirm the publisher can refresh it, or confirm in writing that they cannot. A test that only an administrator can open is the wrong test.

Then force the failure. Withhold the refresh, or point the workbook at a source you have stopped, in a place that is not the live meeting. The named person should say what the room will do. If the answer is "Tableau Next", ask them to open Next and show the same question. If they cannot, the fallback is last week's number, said out loud, or no forecast. Write which.

Do not add a step where the dashboard writes the opportunity. If someone demonstrates a write, stop and ask which field, which user, and what happens when two people trust two numbers. That demonstration is a different project. It does not belong in the test of a view.

The integration is ready when a new analyst can see the source, the cut, the publisher, and the failure without asking the person who archived the file. If the page still says the chart updates Salesforce, send it back. The acquisition in 2019 kept the name. It did not put Monday's number on the opportunity for you.