Hi @lingareddy_Alva 

This might warrant another post to keep the conversation focussed, but I found a couple of things with the custom connector that make it a bit cumbersome to use.

1) I don't seem to be able to have two post operations under /statments so I can't have SetShopDetails . I am looking at use a HTTP PUT but did see some errors when I tired this week

paths:
  /statements:
    post:
      summary: GetShopDetails
      operationId: GetShopDetails

2)  You can't see define a generic response in the YAML so keet the custom connector very flexible.  The idea would be the Power App would have figure out how to handle the response.

responses:
        '200':
          description: Successfully retrieved shop details.
          schema:
            type: object
            properties:
              results:
                type: array
                items:
                  type: object

SO you have define the reponse array for each SELECT request. Indeed with 1) we are looking at having to create a connector per call to a table. Not a great dev experience.