You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-[X] Overloaded functions with rich request options for all Web API operations.
868
-
-[X] Get all pages requests, such as: countAll, retrieveMultipleAll, fetchXmlAll and etc. Implemented in v.1.2.5.
905
+
-[X] Get all pages requests, such as: countAll, retrieveMultipleAll, fetchXmlAll and etc. `Implemented in v.1.2.5`
869
906
-[X] Web API requests that have long URL (more than 2000 characters) should be automatically converted to batch requests.
870
-
Feature is very convenient for big Fetch XMLs. Implemented in v.1.2.8.
871
-
-[ ] Web API Authentication for On-Premise instances.
872
-
-[ ] Intellisense for request objects.
873
-
-[ ] "Formatted" values in responses. For instance: Web API splits information about lookup fields into separate properties,
907
+
Feature is very convenient for big Fetch XMLs. `Implemented in v.1.2.8`
908
+
-[X] "Formatted" values in responses. For instance: Web API splits information about lookup fields into separate properties,
874
909
the config option "formatted" will enable developers to retrieve all information about such fields in a single requests and access it through DynamicsWebApi custom response objects.
910
+
-[X] Simplified names for "Formatted" properties. `Implemeted in v.1.3.0`
875
911
-[ ] Batch requests.
912
+
-[ ] Web API Authentication for On-Premise instances.
913
+
-[ ] Intellisense for request objects.
876
914
-[ ] Use entity names instead of collection names. I have not done an investigation about it but if you, by any chance, know how to do that,
877
915
I will be very grateful for an advice! Quick guess, does it work like in English language?
0 commit comments