Michael Lisby
Michael Lisby
We should be updating the API version already, which I can see is an issue for onprem. Adding a flag to allow overriding the version on generation could be a...
the npm package is not up to date - not even sure whether it works for windows scenarios atm. That being said, the SDK (which our tools depend on internally)...
I think a general description of each of the valid field types is in place. Documentation should be updated.
I just checked on latest (5.6.1), and it's working as intended my side. Which version are you using? Further, I've seen a restart of visual studio or regeneration of the...
I agree, there seems to be some discrepancy with AnyControl. It contains all methods of the included controls, not just the shared methods. I double-checked the documentation (https://docs.microsoft.com/en-us/powerapps/developer/model-driven-apps/clientapi/reference/controls), and the...
It's been mentioned in other issues, but for good measure: At the moment, I'm not aware of anyone from Delegate who implement test of client side code, based on the...
We are well aware that XrmDT relies on a structure that's not 100% up to date, causing issues in some build tools. We haven't had the chance to look further...
Could you elaborate on the issue you're experiencing. Preferably with a minimal code example? Based on the error message you're getting, I think your problem lies in trying to import...
I guess these fields should be Lookups to multiple entities - (Similar to a Customer field, which is typed as Xrm.LookupAttribute). I think the field is created slightly different from...