on
RE:
This is a bug.The standard retention policy fails because no more than 10,000 records can be deleted at once when using the standard job queue. The codeunit 3997 - Retention Policy JQ expects a confirmation with a simple "yes" or "no." However, no user interaction is possible. I believe the issue can be resolved by removing the confirmation (See green) , allowing the job queue to automatically proceed with deleting the next 10,000 records.Please check the code of the codeunit:if Confirm(confirmRerunMsg, true, MaxNumberOfRecordsToDelete()) then ContinueWithRerun := true;
RE:
Amazed this isn't supported yet, dataflows are the worst thing to lose or not have control over.
RE:
The exportData method uses two parameters:exportDataType (optional), choose which data you like to export Summarized data or Underlying data.ExportDataType.Summarized, select this option if you want to export data for what you currently see in the visual.ExportDataType.Underlying, select this option if you want to export data for what you see in the visual plus additional data from the underlying dataset.If not provided the data will be exported Summarized. Power BI Team: Could you be so kind and add the third parameter ExportDataType.CurrentLayout as you already have this option when you click the three dots on the visual and select Export Data. Can you please expose the API for that? Thank you!
RE:
Thank you for your feedback. We are working on adding support for SQL scalar UDFs in Fabric Warehouse. Stay tuned for further updates.
RE:
We need you to improve the pagination synchronization issue.
RE:
Hi @Adnan,Thank you for supporting this idea.The way I am thinking is not to change the behavior of the existing and / or operators we have already in BC.but to introduce new ones.For the and operator, that will be something like: && (as in most languages), AndAlso (as in VB.net) or and_then (as used in PASCAL)For the or operator, that will be something like: || (as in most languages), OrElse (as in VB.net) or or_else (as used in PASCAL).
RE:
Important Implementation! Needed in several Projects.
RE:
UNAVAILIBITY OF IST TIMEZONEAs per my understanding the Microsoft Fabric product is still under development phase and many be multiple features are being worked upon to be included in future releases.Currently, my client is experiencing challenges in using IST time zone. It seems currently there is only UTC time zone available in the product.My client, CSP, Billing Partner are all based in IST time-zone, yet the end user/customer is not able to use IST time zone due to its unavailability.I would request to please develop this feature and include this in the upcoming release.
RE:
Great suggestion, Linda. In addition, it will support a positive the user experience when transitioning from UAT to Production, reducing user profile 'surprises'.