{"id":9614390690066,"title":"Tableau Watch Data Source Deleted Integration","handle":"tableau-watch-data-source-deleted-integration","description":"\u003ctable\u003e\n \u003cthead\u003e\n \u003ctr\u003e\n \u003cth colspan=\"2\"\u003eTableau API Endpoint: Watch Data Source Deleted\u003c\/th\u003e\n \u003c\/tr\u003e\n \u003c\/thead\u003e\n \u003ctbody\u003e\n \u003ctr\u003e\n \u003ctd\u003e\u003cstrong\u003eOperation\u003c\/strong\u003e\u003c\/td\u003e\n \u003ctd\u003eSubscribe to events for the deletion of a data source on Tableau Server or Tableau Online.\u003c\/td\u003e\n \u003c\/tr\u003e\n \u003ctr\u003e\n \u003ctd\u003e\u003cstrong\u003ePurpose\u003c\/strong\u003e\u003c\/td\u003e\n \u003ctd\u003eDetect when a data source is deleted from Tableau, allowing for actions to be taken in response to such events.\u003c\/td\u003e\n \u003c\/tr\u003e\n \u003ctr\u003e\n \u003ctd\u003e\u003cstrong\u003eUse Cases\u003c\/strong\u003e\u003c\/td\u003e\n \u003ctd\u003e\u003cul\u003e\n \u003cli\u003eMonitor data sources for compliance and auditing purposes.\u003c\/li\u003e\n \u003cli\u003eAutomatically clean up related resources when a data source is deleted.\u003c\/li\u003e\n \u003cli\u003eNotify stakeholders or systems about the deletion of critical data sources.\u003c\/li\u003e\n \u003cli\u003eTrigger workflows that depend on the presence or absence of the data source.\u003c\/li\u003e\n \u003c\/ul\u003e\u003c\/td\u003e\n \u003c\/tr\u003e\n \u003ctr\u003e\n \u003ctd\u003e\u003cstrong\u003eProblem Solving\u003c\/strong\u003e\u003c\/td\u003e\n \u003ctd\u003e\n\u003cp\u003eThe 'Watch Data Source Deleted' API endpoint can solve a variety of problems related to data management and governance:\u003c\/p\u003e\n \u003cul\u003e\n \u003cli\u003e\n\u003cstrong\u003eData Governance:\u003c\/strong\u003e Organizations can keep track of changes to their data ecosystem by logging deletion events, ensuring that any deletion of a data source is accounted for and reviewed.\u003c\/li\u003e\n \u003cli\u003e\n\u003cstrong\u003eResource Management:\u003c\/strong\u003e Upon deletion of a data source, associated resources (such as cache, extracts, or dependent calculations and models) can be identified and cleaned up, thus maintaining an efficient and organized data environment.\u003c\/li\u003e\n \u003cli\u003e\n\u003cstrong\u003eProcess Continuity:\u003c\/strong\u003e Automated workflows that rely on specific data sources can be adjusted or paused, preventing errors or misfires caused by missing data.\u003c\/li\u003e\n \u003cli\u003e\n\u003cstrong\u003eAccess Control:\u003c\/strong\u003e Ensuring only authorized deletions occur by raising alerts when an unauthorized user deletes a data source, protecting against potential data loss or misuse.\u003c\/li\u003e\n \u003cli\u003e\n\u003cstrong\u003eNotification Systems:\u003c\/strong\u003e Updating users or systems that rely on the deleted data source so they can take necessary action to prevent disruptions in their work or processes.\u003c\/li\u003e\n \u003c\/ul\u003e\n\u003c\/td\u003e\n \u003c\/tr\u003e\n \u003ctr\u003e\n \u003ctd\u003e\u003cstrong\u003eTechnical Details\u003c\/strong\u003e\u003c\/td\u003e\n \u003ctd\u003eThe endpoint provides a webhook functionality that developers can subscribe to. When a data source is deleted in Tableau, the webhook is triggered, sending an event notification to the specified URL. Developers can then handle this event within their applications or services.\u003c\/td\u003e\n \u003c\/tr\u003e\n \u003ctr\u003e\n \u003ctd\u003e\u003cstrong\u003eLimitations\u003c\/strong\u003e\u003c\/td\u003e\n \u003ctd\u003eDependence on the proper configuration of webhooks and handling mechanisms. Users must have a system in place to consume and react to the webhook notifications.\u003c\/td\u003e\n \u003c\/tr\u003e\n \u003c\/tbody\u003e\n\u003c\/table\u003e","published_at":"2024-06-20T00:30:23-05:00","created_at":"2024-06-20T00:30:24-05:00","vendor":"Tableau","type":"Integration","tags":[],"price":0,"price_min":0,"price_max":0,"available":true,"price_varies":false,"compare_at_price":null,"compare_at_price_min":0,"compare_at_price_max":0,"compare_at_price_varies":false,"variants":[{"id":49657693143314,"title":"Default Title","option1":"Default Title","option2":null,"option3":null,"sku":"","requires_shipping":true,"taxable":true,"featured_image":null,"available":true,"name":"Tableau Watch Data Source Deleted Integration","public_title":null,"options":["Default Title"],"price":0,"weight":0,"compare_at_price":null,"inventory_management":null,"barcode":null,"requires_selling_plan":false,"selling_plan_allocations":[]}],"images":["\/\/consultantsinabox.com\/cdn\/shop\/files\/8f56546f1d26b091189175d81cbdaeb9_25aa0bfd-b861-408a-aa9d-2728a3461727.png?v=1718861424"],"featured_image":"\/\/consultantsinabox.com\/cdn\/shop\/files\/8f56546f1d26b091189175d81cbdaeb9_25aa0bfd-b861-408a-aa9d-2728a3461727.png?v=1718861424","options":["Title"],"media":[{"alt":"Tableau Logo","id":39807376818450,"position":1,"preview_image":{"aspect_ratio":4.812,"height":133,"width":640,"src":"\/\/consultantsinabox.com\/cdn\/shop\/files\/8f56546f1d26b091189175d81cbdaeb9_25aa0bfd-b861-408a-aa9d-2728a3461727.png?v=1718861424"},"aspect_ratio":4.812,"height":133,"media_type":"image","src":"\/\/consultantsinabox.com\/cdn\/shop\/files\/8f56546f1d26b091189175d81cbdaeb9_25aa0bfd-b861-408a-aa9d-2728a3461727.png?v=1718861424","width":640}],"requires_selling_plan":false,"selling_plan_groups":[],"content":"\u003ctable\u003e\n \u003cthead\u003e\n \u003ctr\u003e\n \u003cth colspan=\"2\"\u003eTableau API Endpoint: Watch Data Source Deleted\u003c\/th\u003e\n \u003c\/tr\u003e\n \u003c\/thead\u003e\n \u003ctbody\u003e\n \u003ctr\u003e\n \u003ctd\u003e\u003cstrong\u003eOperation\u003c\/strong\u003e\u003c\/td\u003e\n \u003ctd\u003eSubscribe to events for the deletion of a data source on Tableau Server or Tableau Online.\u003c\/td\u003e\n \u003c\/tr\u003e\n \u003ctr\u003e\n \u003ctd\u003e\u003cstrong\u003ePurpose\u003c\/strong\u003e\u003c\/td\u003e\n \u003ctd\u003eDetect when a data source is deleted from Tableau, allowing for actions to be taken in response to such events.\u003c\/td\u003e\n \u003c\/tr\u003e\n \u003ctr\u003e\n \u003ctd\u003e\u003cstrong\u003eUse Cases\u003c\/strong\u003e\u003c\/td\u003e\n \u003ctd\u003e\u003cul\u003e\n \u003cli\u003eMonitor data sources for compliance and auditing purposes.\u003c\/li\u003e\n \u003cli\u003eAutomatically clean up related resources when a data source is deleted.\u003c\/li\u003e\n \u003cli\u003eNotify stakeholders or systems about the deletion of critical data sources.\u003c\/li\u003e\n \u003cli\u003eTrigger workflows that depend on the presence or absence of the data source.\u003c\/li\u003e\n \u003c\/ul\u003e\u003c\/td\u003e\n \u003c\/tr\u003e\n \u003ctr\u003e\n \u003ctd\u003e\u003cstrong\u003eProblem Solving\u003c\/strong\u003e\u003c\/td\u003e\n \u003ctd\u003e\n\u003cp\u003eThe 'Watch Data Source Deleted' API endpoint can solve a variety of problems related to data management and governance:\u003c\/p\u003e\n \u003cul\u003e\n \u003cli\u003e\n\u003cstrong\u003eData Governance:\u003c\/strong\u003e Organizations can keep track of changes to their data ecosystem by logging deletion events, ensuring that any deletion of a data source is accounted for and reviewed.\u003c\/li\u003e\n \u003cli\u003e\n\u003cstrong\u003eResource Management:\u003c\/strong\u003e Upon deletion of a data source, associated resources (such as cache, extracts, or dependent calculations and models) can be identified and cleaned up, thus maintaining an efficient and organized data environment.\u003c\/li\u003e\n \u003cli\u003e\n\u003cstrong\u003eProcess Continuity:\u003c\/strong\u003e Automated workflows that rely on specific data sources can be adjusted or paused, preventing errors or misfires caused by missing data.\u003c\/li\u003e\n \u003cli\u003e\n\u003cstrong\u003eAccess Control:\u003c\/strong\u003e Ensuring only authorized deletions occur by raising alerts when an unauthorized user deletes a data source, protecting against potential data loss or misuse.\u003c\/li\u003e\n \u003cli\u003e\n\u003cstrong\u003eNotification Systems:\u003c\/strong\u003e Updating users or systems that rely on the deleted data source so they can take necessary action to prevent disruptions in their work or processes.\u003c\/li\u003e\n \u003c\/ul\u003e\n\u003c\/td\u003e\n \u003c\/tr\u003e\n \u003ctr\u003e\n \u003ctd\u003e\u003cstrong\u003eTechnical Details\u003c\/strong\u003e\u003c\/td\u003e\n \u003ctd\u003eThe endpoint provides a webhook functionality that developers can subscribe to. When a data source is deleted in Tableau, the webhook is triggered, sending an event notification to the specified URL. Developers can then handle this event within their applications or services.\u003c\/td\u003e\n \u003c\/tr\u003e\n \u003ctr\u003e\n \u003ctd\u003e\u003cstrong\u003eLimitations\u003c\/strong\u003e\u003c\/td\u003e\n \u003ctd\u003eDependence on the proper configuration of webhooks and handling mechanisms. Users must have a system in place to consume and react to the webhook notifications.\u003c\/td\u003e\n \u003c\/tr\u003e\n \u003c\/tbody\u003e\n\u003c\/table\u003e"}