Mike Stall

> texlFunctionSet.Add(func); see above - we should remove this too. Only call texlFunctionSet.Add() once. --- Refers to: src/libraries/Microsoft.PowerFx.Core/Functions/UserDefinedFunction.cs:249 in 4169003. [](commit_id = 4169003ab9036c970afcfb4a8e196a1511a272da, deletion_comment = False)

> nameResolver.Functions.WithName(udfName).Any(func => func.IsRestrictedUDFName)) suspicious? Adding a new TexlFunction.IsRestrictedUDFName = true is a breaking change. Which means we must keep to a fixed list (currently just AsType, Collect), so why...

> nameResolver.Functions.WithName(udfName).Any(func => func.IsRestrictedUDFName)) talked more. This is also used in other PA Client functions like IsType,Set,UpdateContext ... basically anything that can implicitly define variables. --- In reply to: [2253638869](https://github.com/microsoft/Power-Fx/pull/2559#issuecomment-2253638869)...

Totally possible! Would you like to submit a Pull request to enable this? Possible places to expose this are either: - a new ToString(...) overload on TexlNode. - something on...

Note that the single quotes `'` are not part of the identifier's name - they're just lexical hints. Much like the quotes in `"hello"` are not part of the string...

Can this break existing customers using connectors?

@Sohm22 - can you include some more details about the repro? What product is in this in?

This behavior is by-design. Text() only accepts scalars, not records.

The tabular connector support here is under development. We're working on these classes now and hope to finish and release samples soon. Can you tell us more about your product?...

We _shouldn't_ block a 2.0 release on this: - This is an additive feature, could be dealt with later. - Ideally, we'd steer people towards cross-language solutions. This is C#...