Power Platform DevOps - Connection References

Поделиться
HTML-код
  • Опубликовано: 28 ноя 2024

Комментарии • 12

  • @frenamakenson9844
    @frenamakenson9844 Год назад

    Hey Man, This one is very User Full, 10000 Thanks for sharing

  • @frenamakenson9844
    @frenamakenson9844 Год назад

    Hey man , thanks a lot for sharing 🎉
    ONE quick question
    Is the power Devops more flexible, more option , even better than Microsoft build tools

  • @darespusta
    @darespusta Год назад

    Using your task of updating the connections is there anyway to create the array using variables? More so, automatically populating the connection values from the target environment and placing them as variables in your array input?

  • @MohamedElgharably-g7l
    @MohamedElgharably-g7l Год назад

    First of all thanks Wael for your clear demo.
    I have a little question about this task (Update Connection References) there's no chance to set which solution will change the connection references. in my case, I import three solutions with this pipeline
    correct me if I'm wrong we need to do this task before importing our solution to the upper environment?

    • @UltraDynamics
      @UltraDynamics  Год назад +1

      Hi Mohamed, Glad you found this useful. The task can update connection references across multiple solutions. So the steps would be to import the solution and then update the connection references in each solution using this task.

  • @zarkoradevic3578
    @zarkoradevic3578 Год назад

    Thanks Wael. I have 2 questions:
    1. Your tool for updating connection references is in preview, when is it going to be GA?
    2. I tested it between your import and apply solution steps, and my flow was active in target environment automatically. At the end of this video you mention activation of flows, is there an extra step that is necessary?
    Thanks in advance

    • @UltraDynamics
      @UltraDynamics  Год назад

      There are currently no planned updates to this task so it should be GA in the next release. There is another task which can turn flows on/off if needed. It will depend on the state of the flow in the target env before the pipeline runs.

  • @hayleyrostron4625
    @hayleyrostron4625 6 месяцев назад

    Thank you so much for this. Unfortunately, I am getting this error during the import using the second option from your demo. I Imported to first Dev Environment successfully, but it's failed at the next environment which is another dev (using different IDs on the separate pipeline)
    Request failed with: Forbidden and error: {"error":{"code":"ConnectionAuthorizationFailed","message":"The caller with object id 'd08de8c1-ee81-4e52-969e-3ef48c8fb390' does not have the minimum required permission to perform the requested operation on connection. under API 'shared_commondataserviceforapps'."}} and request url etc.etc.
    I've deleted the dataverse connection and re-created it in the target environment as per some suggestions but this doesn't fix the issue.
    Any suggestions would be greatly appreciated :)

  • @2007pradipta
    @2007pradipta 5 месяцев назад

    grt video. I am confused. Why we need Unmanaged solution. And why we need Unpack and Pack solution ?

  • @alejo708188
    @alejo708188 Год назад

    Thank you, the information is very useful!!, I have a question, can you share the format for $(CrmConnection) into Update Connection References

    • @UltraDynamics
      @UltraDynamics  Год назад

      The connection string follows this format (without the xml tags): learn.microsoft.com/en-us/power-apps/developer/data-platform/xrm-tooling/use-connection-strings-xrm-tooling-connect

  • @varun1987143
    @varun1987143 Год назад

    @Ultra Dynamic, Wael Hamze, Can we pls connect...its urgent