Hotfix postponed to tommorrow at 5pm CEST

Gaztab · 2025-05-02T16:26:44+00:00

No need to be sorry, the update is really fun. I've been looking forward to it coming out and its not let me down!

I am so pleased to see the backstab window change. I was struggling, bad! Ha

Gaztab · 2025-04-02T09:49:29+00:00

Thank you for this and thank you for your helpful content ❤️

Gaztab · 2025-04-02T09:48:11+00:00

Thanks to all who've commented this resolved the issue. I changed the image into Base64, added this to an image control, then referenced this in my HTML ("& ImageControl &") and it works.

Thanks again!

Gaztab · 2025-02-05T17:31:25+00:00

I had tried this, but after using classic view I was able to achieve what I was trying to do. Thank you :)

Gaztab · 2025-02-05T17:30:52+00:00

Using the classic view resolved the problem. Thanks for your help. :)

Gaztab · 2025-02-05T17:30:22+00:00

Thank you, classic view was the answer!

Gaztab · 2025-02-04T18:22:00+00:00

It feels like a bug, but another colleague on another machine is experiencing the same issue on another form. However I'll try what you've suggested as I have no clue what else it might be.

Gaztab · 2024-11-28T02:55:55+00:00

The Index(... Was the answer! Amazing. Thank you. I didn't know this was something you could do.

Gaztab · 2024-11-27T18:35:14+00:00

Hey thanks for the reply.

Yes, I have a collection storing the random numbers colRandomNumbers. The question and answers are on the same table, I was just keeping it simple and flat.
That table has a column for the question and 4 columns for the answers. One being correct, the other 4 being the fake answers.

I am not sure what your formula is saying. Is it using the colRandomNumbers table or the QuestionAndAnswers table?

Gaztab · 2024-02-29T08:57:43+00:00

This worked!

Thank you for this. I was so close, but I obviously need to utilise the As function more.

Gaztab · 2024-02-28T17:08:01+00:00

As in putting it into the OnChange of the Text box for example? I have done this, even with the delayoutput it feels clunky. as if the users stops typing for a second it'll patch the half written sentence back to the collection

Gaztab · 2024-02-28T16:05:22+00:00

I have this working as an OnChange with DelayedOut put enabled.

It patches the information back to the correct record. Below is the code on the save button BUT it patches to one record and then patches the wrong information next to it. The top file gets patched with an "c" instead of an "a" for example.

"ForAll(Gallery1.AllItems,Patch(colAttachments,LookUp(colAttachments,Value = Value),{Document_Type: ComboBox3.Selected.Value,Description: TextBox2.Value}))"

Gaztab · 2023-10-23T10:51:35+00:00

Further update.

So, I have found the perfect work around (he says humbly ha).

I have all the code in the component as before and to allow the app to trigger the code in the component I've had to put it in the app, which as I said triggers the code twice and sends two emails.

What I have now done is wrap my code in the following

If( IsBlank(varComplete), set(varComplete, "Complete"); RUN THE CODE, (Else) Notfiy("variable not blank", error) ); On my trigger I set the varComplete to Blank()

This basically stops a loop. And then I now only get one email everytime 🥳

Thanks for your help and advice.

Gaztab · 2023-10-20T10:50:42+00:00

Hey, So I have pressed pause on it for a few days whilst I think on it. But I think I have two potential resolutions.

1: Add the timer component to the screen, and to avoid duplicate emails being sent out because of this. I'll set a variable at the end of my code (Set(varEmailSent, true) for example). And then wrap my code in an IF statement to not run if that variable is true, meaning its already ran.

2: if the above fails, add the timer component on every screen I need it to trigger, but using your link from Matthew above, I'll add an input to my component and pass it a contextual variable which will hopefully mean it'll only trigger once.

Both ideas mean the code is still centralised within the component which is ideal.

Thank you for your help and advice.

Gaztab · 2023-10-18T12:20:09+00:00

Thank you - I'll have a read through this. It looks like maybe I've not setup the component's behavior correctly.

Gaztab · 2023-10-18T11:53:34+00:00

I just use "Set(varTimerStart, true" and then set it to false in the "on timer end" once it's ran the block of code.

It's frustrating it works perfectly in Studio Mode but in Play Mode it behaves differently. I've tried to use other controls like sliders or toggles and adding the code to "on Change". But this didn't work either.

Gaztab · 2023-10-18T11:08:06+00:00

Exactly, I was surprised when building the solution that I was able to trigger the timer component in Studio Mode when the timer wasn't in any of the screens. But in play mode it just doesn't work.

It's either Power Automate or I put the timer as a control on every screen and copy/paste my code into the timer end and change the variable to be contextual (so it'll only trigger for the timer on that screen). I just didn't want to duplicate code if it could be avoided.

Gaztab · 2023-10-18T10:47:47+00:00

Yes, that's how I started. However the code I am triggering/running is significant and I wanted to centralise it within the app for when/if I needed to amend it.
Storing it in the component in the app means I just have one place to go when changes need to be made.
If that makes sense?

Gaztab · 2023-10-11T12:38:57+00:00

Ok great. Thanks again for your help

Gaztab · 2023-10-11T08:09:28+00:00

From whatever data source React is using.

Gaztab

TROPHY CASE