on
RE:
Hi Team,I suggest refining the Journey creation flow by adjusting the order of the steps, so that "Choose the Type of Audience" follows the form selection. Additionally, enabling users to update or select a form after the Journey is created, without having to delete it, would greatly improve usability and reduce confusion.Thanks!
RE:
Hi Team,I'd like to request an enhancement to the Journey creation flow to allow users to select or change the Form both during creation and after, without needing to delete the Journey. This would reduce confusion and improve the user experience.Thanks!
RE:
It is there, but you have to select the individual series to format. There is currently no way to format it with "all" as the cards may have different data types.
RE:
This would be super helpful, otherwise I need to create two charts to give the necessary granularity choices.
RE:
Dataverse has a limit on the number of requests and will return a 429 Too Many Requests error if too many requests within a period of time as per documented by Microsoft: Service protection API limits (Microsoft Dataverse) - Power Apps | Microsoft LearnCurrently, we found out that there are no configurations available to users/administrators for limiting the frequency of API calls done to Dataverse as this is set-up at their service level.
RE:
Along with Loan management there should be Fixed deposit management as well, this has been a frequent ask from alot of Customers/Prospects I've worked with.
RE:
We are aware that there are service limits for Dataverse API based on this documentation:Our understanding is that these limits are there to restrict if there are too many API requests hitting the Data verse service. Can we check if these limits are configurable in any way, or are there any similar settings we could make use of to limit API calls to Data verse in our environment?
RE:
"...finally inner padding controls the gap between the bars in proportion to the bar size. "When looking at the Line and Clustered column chart, I cannot see this control setting in the X-axis format settings.
RE:
3 years later and this rudimentary functionality is still not implemented
RE:
That menuitem does not clean up the WHSlIcensePlateLabel records. It cleans up the InventDim records related to the licenseplate numbers (not the labels). It executes the below code. I think the idea from Suf still needs some consideration.WHSLicensePlate whsLicensePlate; delete_from inventDimLPCleanupTask where inventDimLPCleanupTask.SessionId == _sessionId exists join whsLicensePlate where whsLicensePlate.LicensePlateParent == inventDimLPCleanupTask.LicensePlateId;