GPT Prompt Builder goes GA and expands to EU,UK,AU

[gbego]

Hello all!

Excited to announce that AI Builder's GPT Prompt Builder is going GA this week and expanding availability across the globe:
🌏 AU, UK : Live now !
🌎 US : Dec 20th
🌍 EU : Dec 21st

Some of the new updates:
✅️ Save, test and share prompts
✅️ Add prompts to apps, flows and copilots
✅️ Dynamic inputs
✅️ Pre-built prompts
✅️ GPT-3.5 Turbo
✅️ Human in the loop validation (optional)
✅️ Prompts are solution aware

Read the blog here: AI Builder GPT Prompts are generally available | Power Automate Blog (microsoft.com) 

And please keep the feedback coming - looking forward to hearing what you can build this new capability!

Gwenael

[ARB_wcc]

What happens with old flows still using the preview connector?

[gbego]

Old flows with the preview connector should still work but we recommend that you migrate to using the new GA Connector for production workflows. When creating a new flow, only the GA Connector will be available. Once users have stopped using the preview connector we will gradually sunset to only support the GA Connector (timeline still TBD).

[ARB_wcc]

@gbego 

I've been experimenting with the new connector since it was released yesterday and encountered three specific issues. See screenshot below for context

First, I'm constrained to using the old designer due to my flows having numerous actions, which the new designer doesn't support. Within this old designer, the new connector seems to malfunction. When I try to create custom prompts directly by selecting "Enter custom value," it redirects me to link an existing custom prompt, not allowing for the creation of a new one with dynamic values from previous steps.

Secondly, in the new designer, creating a new custom prompt opens a separate window, but integrating dynamic values is confusing. When I click on "Add dynamic value," it brings up a text box, and it's unclear if we're supposed to manually input the names of these dynamic values. Unfortunately, this function isn't working correctly either, as it doesn't display a list of potential dynamic values to choose from. I'm uncertain if this is because I'm doing something wrong or a system glitch.

Finally, as previously mentioned, the old connector, while operational, shows a 404 error when trying to expand and view the prompt. The only workaround is to access the prompt through the flow's run history.

These issues are creating significant barriers in efficiently adapting the new connector in my existing workflows, I hope they can be addressed soon.

If you need any additional information feel free to pm me.

[Antrod]

Hi @ARB_wcc ,

Thanks for the details and sorry about the issues you're facing with the new experience. Please rest assured that we are fully committed to continuously improve this experience. Let me try to provide some answers to you:

• The 404 error that happens when displaying the old GPT action in the old designer is acknowledged on our side and we are working on a fix that we should deliver next month. There are some workarounds to retrieve the prompt in the meantime, so you can create a new prompt using the new experience:
  • Use the flow run history as you suggested.
  • Export your flow and look for the definition.json file in the package and you should be able to see the prompt text inside (a bit more technical).
• The old flow designer is meant to be deprecated and therefore all new experiences may not work the same way in the old designer compared to the new one. This is why the experience for the new AI Builder GPT prompt is degraded in the old designer and it may happen with other upcoming features. The overall strategy here is to improve the new designer so it reaches the same quality (and even more) that the old designer.
• Speaking about the new designer, the team in charge of this feature is fully committed to make it stable as soon as possible. They are right now working on making rid of this action limit that you are talking about. Hope this will reach you soon!
• If you don't have any choice and need to use the old designer, as a workaround for AI Builder GPT prompts, it's possible to create the prompt in the Power Automate portal / AI hub, and then select the newly created prompt in a flow.
• The dynamic value that you can now add inside the prompt is something new that allows you to create input parameters for your prompt action so you can fill them with dynamic values in the flow designer. This can be powerful to pass dynamic values into your prompt across various experiences (flows, apps, chatbots).
  • Let's say that your prompt is "What is the speed of light in [location]?" where [location] is a dynamic value that you defined. You can now run your prompt by passing a value to the location as parameter.
  • But we understand your confusion here and we'll try to improve our design to make things a bit clearer.

Stay tuned, we'll keep you informed! And please continue providing your feedback, it greatly helps us.

[ARB_wcc]

@Antrod I appreciate your insights and the team's efforts.

For now, I'm opting to continue with the old preview connector and hold off on updating my flows until the current issues are eliminated.

I've also encountered another issue related to the new SharePoint UI which seems to have been overlooked in testing with flows (posted here). It's disheartening when these updates seem rushed and possibly tied to deadlines rather than readiness.

Your commitment to improvements is reassuring, and I hope for a resolution that ensures robust and thoroughly tested updates in the future. 

[Aspereira]

There is no point in forcing the user to use a new designer. If you still have several bugs in addition to being slower to execute actions.

[mt_gptbuilder]

@Antrod  Can you elaborate on using dynamic values in flow designer ? Do I have to create a variable before being able to use it in the GPT prompt ? Is there any other way to get output from previous step as input into custom GPT prompt ?

Thanks 

[ARB_wcc]

@takolota just curious to know if you had the time to update/test your flows with this new connector. I've learned recently that old prompts are not performing the same and apparently there's an underlying issue where the prompt works fine in the test view but when running the flow it spits out a completely different output that has nothing to do with the results we see in the test view.

[takolota]

@ARB_wcc 
I didn't get very different outputs in the little bit of testing I did with the new action. But there were several other things I noticed...
-After entering a custom prompt, if I went back to edit it then all the linebreaks were removed. I hope this doesn't affect the accuracy of the response output when it is less clear that there are larger distinctions between lines that normally had multiple line-breaks between them. 

-I can not smoothly transition over to the new prompt action in the template that potentially many hundreds of people use because adding a custom prompt to a flow prevents that flow from being imported to a different environment in a Solutions package. I need this to be fixed to keep my template up to date & easier to use.

[ARB_wcc]

Haven't done enough testing either and so far I also don't like that I'm forced to keep prompts outside of the flow, doesn't make much sense to me. If anything we should have both options, to write the prompt in the flow itself or link to an external prompt. 

[takolota]

@gbego @Antrod 

When will solutions support importing packages with custom prompts?

Currently Microsoft has a couple of my projects in a bad catch-22 situation where I can't edit the prompts of the previous GPT preview action because it is deprecated, but I also can't switch to the new GPT prompt action without losing the ability to export & import solutions to different Dev & Production environments.

[CedrickB]

See my reply here Re: Question for everyone : How are you using Crea... - Page 3 - Power Platform Community (microsoft...

[Plinderoth]

Solved: Turns out that turning on Copilot for Power Apps in Power Platform tenant settings also enables AI Prompts.

When trying to go to AI Prompts in the menu in Power Automate we receive the error message:z

This feature has been disabled

AI prompts have been disabled . Please contact your administrator.

As administrator in Power Platform I can't find any documentation about how to enable it. The tenant is located in Europe.