on
RE:
This is very restricting limitation. It has been a major roadblock for us to move all our reporting to PBI and decommission our legacy reporting system. Any modern tool should allow at least 1 million row export limit.
RE:
Is this really still not a thing? Seems like this should be standard for a reporting tool.
RE:
Great idea and it has my vote!
RE:
This should have been in the build from the start! Please implement this functionality.
RE:
The Microsft team has reached out to us at Accelo, and is working to release a fix for the connection error. They estimate it will be live by February 7th.Thanks everyone for your support on this idea!
RE:
Is there any update here? This is a big requirement for our org also!!
RE:
This should be a key feature... our enterprise is planning to use a medallion architecture where bronze and silver ETL processes are done through notebooks and LH, however, we also want to leverage the use of a metadata config DW. We need a way to update from those ETL notebooks attributes on the config WH such as LastExecutionDT...
RE:
In the first comment by the microsoft employee here it says: "However, it required the user was configured to use the Track All setting. More recently this was changed to support each of the tracking options."Is this correct? Is it not only the "All Messages" option the automatic tracking happens?
RE:
Dear Beatriz or other PM at MS,It seems you've actually fixed this! When you choose Refresh processes in Product lifecycle states there's now two options on status Obsolete:Sales order Sales order creationWe have run tests with Sales order enabled and Sales order creation disabled and it seems to solve above problem!We'd be delighted to get your comment on this if possible!Best regards,Johan Lindbom
RE:
This would be a great feature, currently we use an Azure Logic App to achieve something similar to monthly refreshes