RE:
Upvoted - this desperately needs a fix.
RE:
Hello, You can create a pareto chart quickly and easily using "Pareto by sio2Graphs" or "Pareto+".sio2Graphs
RE:
Hi,
I've visited releaseplans.microsoft.com and was wondering if you would be interested in promoting your site to our audience of up to 30 million?
In addition to this, we have over 3.4 million followers on social media where we can also promote your site.
If this is of interested, do not hesitate in replying back
If you are not interested, simply ignore this email.
Thanks,
Barbara
Unsubscribe: https://removeme.live/unsubscribe.php?d=releaseplans.microsoft.com
RE:
How is this seriously not resolved yet? This has been open for 2 years since the "workaround".
RE:
Yes, Is very annoying that notebooks are saved on root of workspace. Same happen with APIs
RE:
Yes. And I would like that workspace folders are similar that repository folders with a 1:1 relation between a jupyter notebook (ipynb) and a workspace notebook. I would like to use any IDE I want (Code, Pycharm, nvim, etc) and add pytest, linters, etcetera.
RE:
I agree wholeheartedly that this function would be ideal
RE:
Be able to send a confirmation email (autoresponder) to the person who fills out a form every single time they fill out the form. Currently we have to set this up through a Customer Journey. But a contact can only go through a journey once. So, if they come back to a form again and fill it out again, they will not get a confirmation email.
The confirmation email on any form should be sent to the responder every single time they fill out the form, no matter how many times they fill it out.
This is standard form/marketing automation functionality.
RE:
Problem: Currently if a form submission fails after the user has hit 'submit', this is recorded and shown with the form submissions. We only see it if we go into the form submissions; so we may miss that there are failed submissions, because we are likely not going into form submissions everyday, especially if we have set up journeys to process our form submissions.Suggested solution: include in form set-up options (per form preferably, or globally) a user who can be notified when a form submission fails. That way they know to go and check and handle the failure.Alternatively, provide help information enabling the user to set up their own notifications using power automate by advising what table the failed submissions are recorded to.
RE:
At the moment, for EVERY Form we created, we have to manutally create 2 workflows to notify staff that a form has been submitted. This is CRAZY! ClickDimensions has had, for years, an 'Actions' tab that asks you what should happen when a form is submitted, ie, 'Email X staff members', 'Send an Email to the person who submitted the form'; etc, etc.
This isn't rocket-science, and it's a MAJOR oversight on Microsoft's behalf. Users shouldn't have to create Workflows, Customer Journeys, and/or anything to simply get notified when someone submits a form! It's a given that the person running a campaign wants to know if someone has signed up for something, submitted a form, whatever. The Form's Task Pane should have 3 tabs, like, ClickDimensions:
TOOLBOX | PROPERTIES | ACTIONS
The Actions tab should have different options for what has to happen when a Form is submitted: Email the Owner of the Record; Email the Owner of the Form; Email the person who submitted the form to thank them; etc, etc, etc.