Getting some REST, playing with MATCHES, and digging the Graph

Version 1

    It is almost summer here in Seattle, but our engineers are still spending a lot of time indoors working hard on some new feature and updates to the Developer Platform. If you missed our monthly Sprint demo last Wednesday, this blog post gives you an overview of the announcements.

     

    We started with Jac Fitzgerald, Senior Software Engineer. She has been working on a new search parameter for the REST API. Thanks to her work, you can make a more powerful and quick search.

     

    Today when using the REST API to search for a workbook, you have to specify in your call on which field you want to filter on such as name, tags, and createdAt. Your endpoint looks like: /workbooks?tags:eq:[YourKeyword]

     

    This is great. However, the downside is that you must know upfront if your keyword matches the name of the workbook or the tag.

     

    In 2019.3, we are making your life easier with a new call that is using a new filter calls: matches. This filter is going to search for all the available fields with the value you are searching for. Your endpoint is going to look like: /workbooks?matches: [YourKeyword]. Thanks to this new call, you can have multiple results with fewer calls.

     

    Jac didn’t stop there; she also showed what she has been working for 2019.4. She is working on a way to get a single workbook or data source via its content URL. Today, you need the workbook/data source ID to query it.

     

    Then, we had Graeme Britz; Senior Product Manager talked about the new API for the Tableau Catalog. Tableau Catalog is planned to be released with Tableau 2019.3 as part of the data management add-on. The Catalog will allow you to track data lineage and how data and content is being used on your site, in addition, it also allows users to search for datasets, gives more tools to communicate data quality, and surfaces more information to viz viewers to understand the vizzes they are using. With the catalog, one new API is coming, and new endpoints are going to be added to the REST API.

     

    The first one is the Metadata API that has been demoed a few months ago at our Sprint Demo. It is a read-only API that will allow you to query for lineage and schema metadata that we have in the catalog and see all internal and external assets referenced on your site. The Metadata API is our first GraphQL API.

     

    The new REST API calls are also going to be added to support editing, managing and modifying these new external assets types that are going to be added to Server through the catalog. For example, to manage the metadata for a database and table over API. You can also programmatically set new data quality warnings, that is a new feature coming with the catalog.

     

    If you are interested in learning more, join the Developer Program, and watch the recording of the last Sprint Demo.

     

    That’s it for this month, stay tuned for our next month Sprint Demos in July!

     

    Join the Developer Program today to be the first one to know!