Skovlund
Skovlund
I'm not sure if the get-/setLabel functions are actually a mistake or if the documentation has simply omitted them by mistake. The documentation for the individual functions states that they...
The [documentation](https://docs.microsoft.com/en-us/powerapps/developer/model-driven-apps/clientapi/reference/attributes/getvalue) states that it should be a `Date`. And since the top-level context returns a `Date`, I think it is safe to assume that is the intended behaviour. In...
TSource and TArgs allows specification of the return types of `getEventSource()` and `getEventArgs()` respectively. These are not typed by default as the return types depends on where the functions are...
That seems like a reasonable conclusion, though I would just go with the `Xrm.AttributeCollection` myself. Typings offer a lot, but if a column is removed from your editable grid the...
@misoeli I've looked through the changes and it looks fine. However, I've not tested and therefore have not verified that we have caught every instance of "Xrm". @majblackburn I'm not...
As magesoe says `Filter.makeGuid` should solve this for you. When Dynamics 365 resolves your filters, it ignores braces '{}' around your guids as well as casing. I made the below...
Hi Mathias I'm not familiar with strictest, so it is not obvious to me, what issue you are experiencing when using strictest with XDT. Is your issue with the XDT...
I think we all misunderstood the intended use of `Xrm.AnyControl`. It is intended as a catch-all when working with an unspecified control, where we don't want to limit typings to...
This should be fixed already. The fix was merged in #62 (specifically in this [commit](https://github.com/delegateas/Daxif/commit/303c180bc370997373d8809ccb9a6fe39a56c0ba)). We thought it was released as part of Delegate.Daxif version 5.0.0, but on closer inspection...