So smart, i was building the same thing 2 weeks back, had the exact same set up but i used substitute to replace the key words with real values. This is going to transform my app!! thanks!
Nice one. The benefit of this demo being the substitution on the number of fields is dynamic? I realised during build, nested substitutions would be a pain and fixed number. Meaning the expression would need updated. Let me know how you get on.
Now a prompt library using OpenAI Assistants with every user logging their own conversations using saved chat ID's outputting JSON which is used to populate SharePoint/Dataverse/SQL/etc using this method would be great!
I'm curious, you'll have to explain your thinking as I only believe this would be useful on the return lines when joining the paragraphs but as the rest of the document is dynamic, including the text inputs, I don't understand where else? If I pass a string with interpolation inserted, it won't evaluate as it is already a string. The interpolation needs to be part of a fixed expression? But I am interested if there is an alternative as I learn too 👍 As an example, if I insert $"Hello {User().FullName}. The current date is {Today()}." into SharePoint List and pull it through in the PowerApp, it returns $"Hello {User().FullName}. The current date is {Today()}." If I insert the same expression in a Text Label, I get Hello DamoBird365. The current date is 19/02/2024. Let me know what you are thinking?
I'm now thinking that the coalesce could be combined with three sources. Text input, standard values from a taxonomy and then the other strings. Placeholders like user / email could be inserted into these strings automatically using this method and coalesce.
Yes definitely gave me inspiration as always. Thank you Damien.
Nice to see you using Power Apps - elegant as always. More power to you!
So smart, i was building the same thing 2 weeks back, had the exact same set up but i used substitute to replace the key words with real values. This is going to transform my app!! thanks!
Nice one. The benefit of this demo being the substitution on the number of fields is dynamic? I realised during build, nested substitutions would be a pain and fixed number. Meaning the expression would need updated. Let me know how you get on.
Great Video 👏 what if want to change controls? Like date picker , drop down etc
You could duplicate the controls and only show the one relevant?
Nice demo🎉!
Now a prompt library using OpenAI Assistants with every user logging their own conversations using saved chat ID's outputting JSON which is used to populate SharePoint/Dataverse/SQL/etc using this method would be great!
Hi Simeon. Yeah I love it 😍 great idea 💡 have you seen my video dropped today? Mistral Large LLM in Azure. Very exciting.
He is the best!
Any reason for not using string interpolation?
I'm curious, you'll have to explain your thinking as I only believe this would be useful on the return lines when joining the paragraphs but as the rest of the document is dynamic, including the text inputs, I don't understand where else? If I pass a string with interpolation inserted, it won't evaluate as it is already a string. The interpolation needs to be part of a fixed expression? But I am interested if there is an alternative as I learn too 👍
As an example, if I insert $"Hello {User().FullName}. The current date is {Today()}." into SharePoint List and pull it through in the PowerApp, it returns $"Hello {User().FullName}. The current date is {Today()}." If I insert the same expression in a Text Label, I get Hello DamoBird365. The current date is 19/02/2024. Let me know what you are thinking?
Hi / your vid is not letting me watch at a faster speed. Was that a setting on your end?
Nothing I’ve done 😱 is it simply not an option?
Thank you! It’s a bug on my app. I emailed youtube. Sorry abt that!
@@JenMayB not a problem 👍
Can you use columns in a sharepoint list .?
You certainly could 👍 what’s your use case?
❤ Great use case for Coalesce() Well done Damien! 👍Thanks for posting that!
I'm now thinking that the coalesce could be combined with three sources. Text input, standard values from a taxonomy and then the other strings. Placeholders like user / email could be inserted into these strings automatically using this method and coalesce.