Skip to main content

Access to ADMM data

Syniti Knowledge PlatformMigrate

Very often we are asked to create reports from ADMM data. In ADM we were able to get any information since we had access to its database but now we are limited to the data in MIG views in which we don't have all the tables and sometimes the views doesn't have all the fields from its tables.

I would really like to have all the tables from the system available to be refreshed via MIG views to enable us creating any report needed by the client and solutions via construct.

Some examples:

  • User / role: There's a view with this information but the Support told me it is deprecated and will probably be deleted. This view should be updated with the correct information

  • Design: MIGALLDATASET_TABLES doesn't have the dataset ID, index, datasource,…

  • Mapping: Missing views for dataset's target and source tables (with index, active flag, …)

Posted by Marcos Moraes ·
Status: In Progress3 comments

Log in to comment and vote

Comments3

  • John Munkberg

    Team•

    Mar 7

    Update - the platform is working to also expose the data via the OData layer. OData is generally simpler because it’s mostly flat - like tables. First phase is to expose the DQ Reporting metadata - which drives the DQ Dashboard - as OData so it be extracted via Replicate, or directly consumed by our new Construct Preview into the Charting Components.

    Migrate is exposing the mig views as OData, and will introduce the option to expose some Migration Reports or Migration Exports via the OData layer as well.

  • John Munkberg

    Team•

    Oct 23, 2024

    The goal is to publish Public APIs to support external access to READ/WRITE data into the cloud. Some of these APIs will be useful for extracting application data from the cloud.

    But the GOAL of SKP is move away from everyone building stuff ON TOP OF the product as this create unnecessary work for every project, and creates a very large risk in that the Cloud Product is always evolving. Things you build on top of the data model will eventually break because we are going to continue to evolve the data model independant of what folks are doing.

    While the SKP API should remain fairly stable, as an API should, the MIG views in Migrate will change dramatically as we begin to move Migrate to become fully integrated into the multi-tenant cloud data model.

    Current plan is basically align the MIG views with the new Migrate Public APIs, and eventually to deprecate the direct access to MIG views. However, once Replicate can pull data from Public APIs you would have access to the same data, just via APIs and not Table access.

    A better request if for us to add the missing functionality into the product, with enough Configurability to accomodate special request / situations. Don’t extract the data and write a new dasbhboard, just use the new “Custom Dashboard” feature in the platform to do what you need (for example)…

    • Marcos Moraes

      •

      Oct 25, 2024

      Thanks John!

      I will definitely keep posting ideas for new features!

      I think the API will be very useful, as sometimes the project needs a feature within a timeframe that isn’t feasible for our product team to meet.

      Additionally, it allows us to test the idea with the customer and iterate through the initial development cycles, resulting in a more cohesive concept.

      And also allow us to participate in demo jam =)

      I found out about the SKP API a few weeks ago and we are working to build a process in Boomi to read from it.

      Is there a different API to pull migrate data?