Power-Fx icon indicating copy to clipboard operation
Power-Fx copied to clipboard

Power Fx low-code programming language

Results 179 Power-Fx issues
Sort by recently updated
recently updated
newest added

We log the below expression and then see an InvalidOperationException thrown. The card does have two Dataverse tables attach so I suspect they try to assign these to variables. Still,...

MS_CARDS

This test fails [Fact] public void CheckParseSuccess() { var config = new PowerFxConfig(); var engine = new Engine(config); var parse = engine.Parse("If(Len(x) = 0, y, x)"); var r = RecordType.Empty()...

TexlFunction.TryGetParamDescription only works on current thread's culture. We should allow it to pass in a culture. search for this issue in code to see more.

Comments 2 Fx variation of Nl2Fx supports converting comments into code suggestions. Comments could be anywhere in the formula. A formula can have inner scopes due to the use of...

As we progressively add more functions to BuiltinFunctionsCore, greater is the risk of UDF breaks. https://github.com/microsoft/Power-Fx/blob/3e4e9fb5c12805185144cf9fa59f608418ed4ba4/src/libraries/Microsoft.PowerFx.Core/Syntax/UserDefinitions.cs#L101 --- Refers to: src/libraries/Microsoft.PowerFx.Core/Syntax/UserDefinitions.cs:103 in aa1dd48. [](commit_id = aa1dd4848e9454aafbe2fa99c8481edc687011f8, deletion_comment = False) _Originally posted...

The interpreter doesn't implement all Power Apps functions yet. See list of power apps functions: https://docs.microsoft.com/en-us/power-apps/maker/canvas-apps/formula-reference List of functions implemented in Interpreter is at: https://github.com/microsoft/Power-Fx/blob/main/src/libraries/Microsoft.PowerFx.Interpreter/Functions/Library.cs Looking at history for that...

good first issue

For Expression where the user by mistake assigns the void type to the record field, e.g. `{out : Remove()}` we give the below error. `Incompatible type. The item you are...

The following unit test fails but it should not. public class LazyRecordType : RecordType { public LazyRecordType() { } public override IEnumerable FieldNames => new string[1] { "SubProperty" }; public...

We initially supported relationships for resiliency to name collisions (we would grab the associated data source info off of them) but this just resulted in further issues for analysis/translation later...