Make pulling Data from API sources EASIER with low code UX
In many cases we need to pull data using API calls. Many times - main API call with nested API calls.
For example:
main call: www.someapi.com/v2/students - gives us list of students.
nested call: www.someapi.com/v2/{student_id}/courses - gives us the list of enrolled courses for each student id
another nested call: www.someapi.com/v2/{student_id}/{course_id}/grades - gives list of grades per student per course
etc.
Many times - the results have pagination mechanism.
Also, many times the API sources have rate limits so there should be an option to wait for a minute or so between some number of calls.
Most of the Fabric users are low code data analysts that want a simple and effective way to get the data from such sources using a simple UI and save the results in a Data/Lake house
Today, using Copy Activity / REST Activity / For Each activity is so very clumsy and confusing. Also there are limitations of number of rows to pull.
Please make this task, not just easier for us, but make it an AWESOME experience.
We believe you can make it happen.
Thank you in advance!
1 Comment
- fbcideas_migusrNew MemberStatus added:Needs Votes
Recent ideas
OneLake Catalog full-text and content search
Why is it not possible to search OneLake by item description or even content? So I was thinking about how a user can find a table if they don't know in which lakehouse it is located? Why can't you se...TePe8 hours agoHelper IVPlanned1.1KViews21likes5Comments