Tab autocomplete wipes out chunks of formula

(1) Share

Report

Posted on by SimonMeadows

171

I have noticed this happens quite a lot while editing formulae.

I have a formula in which I am adding an If() to test something before performing the next action.

The formula is underlined because I have split the ForAll() function but not yet completed all required parameters of the If().

For me it is normal to first code the working formula then add validation If()s later once i know the base formula works.

While writing a datasource I press TAB to autocomplete the datasource name.

Instead of filling in the text offered it removes the rest of the formula and tries to force some of the parameters of the other functions into the required parameters of the LookUp function I am currently writing.

What is the expected behavoiur of autocomplete when editing in a formula that is incomplete within another function?

In most coding environments autocomplete usualy only operates on text adjoining the cursor and has no effect beyond the next white space.

Also, is there a to use TAB for indentation of code?

Currently it will always insert an autocomplete even after CTRL ENTER on a blank new line.

Categories:

Building Power Apps

I have the same question (0)

All responses (3)

Answers (0)

v-yamao-msft on at

Like (0)

Report

Hi SimonMeadows,

I can reproduce it just for one time, when using Tab to edit a formula that is incomplete within another function, the formulas after the cursor are removed. While the next time I try the same action, this issue doesn’t occur.

I am always using Enter key to automatically enter values into the formula. I never occur this kind of issue on my side when using Enter key.

Best regards,
Mabel Mao

Was this reply helpful? Yes No
Meneghino 6,949 on at

Like (0)

Report

Hi both, I have come across the same issue and have lost bits of formula.
Also, there seems no easy recovery from this, since pressing Esc will not restore the formula to what it was before starting editing, I believe.

Was this reply helpful? Yes No
Michael Microsoft Employee on at

Like (0)

Report

Thanks for reporting the issue, @SimonMeadows. After digging into the code, it seems that the issue is the tokenization when the name is not closed with a ' character. As a workaround, you can add the closing ' character before accepting the suggestion. I will be working on a fix that will at least allow the tokenizer to also recognize a new line as the end of the token.

Was this reply helpful? Yes No