Currently the dataset sample doesn't use opendatasetitem
Is there any reason for this? Using opendatasetitem has the advantage that if there is a CommandBar Command for Mscrm.OpenRecordItem - it will use that instead.
Also - the documented API isn't quite correct it seems. It is documented as accepting an EntityReference
but in fact it needs something like:
var entityRef = { LogicalName:logicalName, id:id }; this._context.parameters.sampleDataSet.openDatasetItem(entityRef);
cc/ @HemantG
Solved! Go to Solution.
hi Scott,
Regarding the bug about openDataSetItem input argument, we will fix this and we expect it will release to North America at end of October. Thanks for reporting!
Your suggestion on openDataSetItem should be in sample is correct. I do not remember details, but I feel it should be:
1) We need to present 'context.navigation.openForm' sample in whole sample suite, which we thought is a more significant API than openDataSetItem
and 2) The bug you mentioned
That made us choose the 'openForm'.
hi Scott,
Regarding the bug about openDataSetItem input argument, we will fix this and we expect it will release to North America at end of October. Thanks for reporting!
Your suggestion on openDataSetItem should be in sample is correct. I do not remember details, but I feel it should be:
1) We need to present 'context.navigation.openForm' sample in whole sample suite, which we thought is a more significant API than openDataSetItem
and 2) The bug you mentioned
That made us choose the 'openForm'.
Ok great - thanks for the update.
Stay up tp date on the latest blogs and activities in the community News & Announcements.
Mark your calendars and join us for the next Power Apps Community Call on January 20th, 8a PST
Dive into the Power Platform stack with hands-on sessions and labs, virtually delivered to you by experts and community leaders.
User | Count |
---|---|
5 | |
4 | |
2 | |
2 | |
1 |