on
RE:
@Sarah Kwan. This is a huge one for us as well! We are working to customize this in the interim. If you have already done so I would love to know how you were able to accomplish this! Thanks so much!
RE:
I am so glad to see this is being considered and this was posted as an idea. This is something that all ecommerce applications I have ever worked with have and this is an absolute must! I wish I could vote 100x for this :). Thanks so much!
RE:
Hi All,Seems Currently there is limitation in Business Central for the Batch API Request ,current threshold is set 100. This is a “by design” limitation: in a batch API call, you cannot send more that 100 operations at atime and you have no way to override this limit. Current error - If There more than 100 records in Batch API Call500 Internal Server Error: "{ "error": { "code": "Unknown", "message": "The current batch message contains too many parts. A maximum number of '100' query operations and change sets are allowed in a batch message." }}". Idea - As 100 Threshold is very minimal we want to request please update this limit or make it configurable to admin user ,this will help us to send more records in batch API. Kindly vote on the idea.
RE:
We need this urgently. This will be a very important improvement.
RE:
I see that the post has been open for more than 3 years... Is there an API to rename dataset and Report in PowerBI?? If yes could you please share the documentation for it.... From the PowerBI web app am able to rename a dataset.. so it would be great if we have the same feature as an api as well...
RE:
This would save tons of time for us!
RE:
This would be such a time saver!
RE:
Adding columns one by one using DAX functions can be time-consuming. For example, if you want to display new functions for each month from January to December, it is time-consuming to input each month individually.
RE:
that's a high value incrementand best would be if you could also let the customizer to control if he list appears (by default) expanded or collapsed.(maybe have a collapse/expand all in the navigation would be of added UX value).to you put the cherry on top, add count to itScenarios: I had several times the requirements that in an existing solution where you had anentity 1 (e.g. event) and an intersect entity 2 (e.g. participants) which contained a lookup to an account (B2B) and contact (where you managed the event participation processes including status such as no show or cancellations) -> no way direct N:N relationship with hidden intersect as you need the intersect entity business process wise.and the entity 3: Account (or contact in a B2B scenario the contact participates on behalf of the account...). You wanted certainly have the list of participants, but also the managers just wanted a list of (unique!) Accounts on one glimpse without having to fidget around with grouping ("too many clicks")... or (worse yet) manually collapsing the 100+ participants. As a YY manager, I want to open the AB form and see the list of unique Accounts, unique Contacts (best including total count) in separate thanks to default grouping and default collapsed display.Use cases: e.g. List grooming (Oh, I see my key account has not yet one of their contacts signed up to our flag ship event, ... I will follow-up...!), quick information from how many accounts do we have contacts participating on this event. Instead of events you could use any other such as Opportunity and line item grouping by product type and more.
RE:
I see that in release 24 the check that doesn't allow to use this documents with advanced locations has been removed.So I think that this idea has been solved.