I've been trying these samples on macOS 11.6.1
I am using .Net: 6.0.101

but I get the following error trying the WebDemo and ConsoleREPL:

The type initializer for 'Microsoft.PowerFx.Core.Texl.BuiltinFunctionsCore' threw an exception

To fix the issue, I've locally modified the samples taking inspiration from microsoft/Power-Fx#71 (comment)

ConsoleREPL

To fix the issue I've added:

CultureInfo.CurrentCulture = new CultureInfo("en-US");

before this ResetEngine(); line:

Before:

After:

Web

Since I could not find ASP.Net redistributable for .Net Core 3.1 for Mac OS X,
I've replaced this line:

to read

    <TargetFramework>netcoreapp6.0</TargetFramework>

instead.

Then, I've changed this line:

to read:

        public RecalcEngine GetEngine()
        {
            // If the engine requires additional symbols to load, server
            // should find a way to safely cache it.
            CultureInfo.CurrentCulture = new CultureInfo("en-US");
            var engine = new RecalcEngine();

instead.

Please notice I've tried to just pass new CultureInfo("en-US") as an argument to the RecalcEngine constructor, but that didn't solve 🤷

Pardon me if there is a simpler solution but I'm very new to .Net! 😆

The above solves for me on Mac OS.
Before:

After:

Running the code from https://github.com/microsoft/power-fx-host-samples/blob/main/Samples/Dataverse101/Program.cs but changing the formula to:

AsType(First(Accounts).Owner, Users).'Full Name'

As described in the docs. this should cast the polymorphic Owner type to a user and return the name of that user. Instead it returns an ErrorValue with a message of "Runtime type mismatch".

what a great sample! It builds and runs perfectly on Windows, but not so on mac catalina.

the service builds and runs. I had a problem with the app. it showed a "failed to find WebAssembly" message when i issued "npm start" command.

solution: node does not run alongside graalvm. After removing graal, the app shows the page at port 3000.

however, the page is not functional, there is no intellisense and no evaluation.

I think this is the best case:

Record syntax is { < field >: < value >, ... } without quoted field names.
    Example: { Name: "Joe", Age: 29 }
Use the Table function for a list of records.  
    Example: Table( { Name: "Joe" }, { Name: "Sally" } )
Use [ <value>, ... ] for a single column table, field name is "Value".
    Examples: [ 1, 2, 3 ] 
Records and Tables can be arbitrarily nested.

Why we need format this StringValue?

The TableTransform fails because the field name "Name" is used in the record twice. Replacing second Name: in the yaml with a different field name solves this.

Diff: = Score2 - Score
Name&Diff: = Name & Diff
Total: = PreviousRecord.Total + Score
RowDiff: = Score - PreviousRecord.Score

Name,Score,Score2,Diff,Name&Diff,Total,RowDiff

To see issue, select the Start Windows logo Start button, then select Settings Gear-shaped Settings icon > Accessibility > Contrast themes. This issue occurs when selecting the Aquatic and Desert themes.

Hi guys, any plan to have an example Power-Fx running on Blazor

I'm not sure if this should be directed to the Fluent UI or Monaco teams instead, please advise if so.

I'm trying to host the formula bar within a Fluent UI <Panel> control. The formula bar appears as expected, but the autocomplete list does not appear. To repro, edit the PowerFxDemoPage.tsx component, add the import:

import { Panel } from '@fluentui/react/lib/Panel';

and wrap the entire contents of the component in a <Panel>:

<div>
  <Panel isOpen={true}>
    <h3>Context</h3>
    ...
    <FetchData />
  </Panel>
</div>

I am starting to work with the formula bar and want to work it into my own react apps. However, when I try to force the npm install, I am seeing a dependency error:

npm ERR! Could not resolve dependency: npm ERR! peer react@">=16.3.2-0 <17.0.0" from @microsoft/[email protected] npm ERR! node_modules/@microsoft/power-fx-formulabar npm ERR! @microsoft/power-fx-formulabar@"*" from the root project

I have re-run the install with --force and so far I am not hitting any roadblocks (actual installed React v is 17.0.2) but the control should be supporting something at least close to most recent React ver (which is over 18 now).