RE:
Same goes for the 'Show Dashboards' button - please give us the possibility to hide those buttons, as some customer do not need/use them at all and wishes a clean ribbon bar in their environment.
RE:
Needed indeed
RE:
Informative, thanks for sharing
RE:
Looks like an excellent idea!
RE:
I love that this is ranked #5 on the list, has been around for almost 3 years, but Microsoft doesn't even bother to respond.We host BC for our customers, so the only thing that makes sense to at least give them sovereignty on the authentication is to use Entra ID for authentication.Not being able to use security groups is ridiculous, every single user needs to be managed individually. We have customers with 500+ users. We get a request about it from time to time but I'm honestly surprised by the "capacity for suffering" our customers have...
RE:
Definitely needed
RE:
Adding the ability to post from ledger to Project or Project to Project via intercompany would be a huge time saver for us. In the meantime this functionality being unavailable is costing our team quite a bit of hours to our monthly close process. Help please :)
RE:
Really critical if you are working with support departments and IVR mens where customer numbers and case numbers are requested. The audio feedback of a tone would make it so much easier to know if you've entered the numbers correctly with each click.
RE:
I have a client who currently uses this functionality and is waiting on a fix.
RE:
This is a major issue we're experiencing as well. We need to be able to edit live segments based on growing audience over time. There is only so much pre-planning that can be done when building the segment when we are creating long term nurture content. On Microsoft's known issues they say "Today, users can't edit a segment that is being used in a live journey in Customer Insights - Journeys. To be able to edit the segment, stop the journey, and then make the edits to the segments." This makes it seem like we can pause the journey and restart it after finishing segment edits. However, this is not the case. When we go to stop the journey we get a warning "Once this journey is stopped, it cannot be restarted. A stopped journey has to be recreated before going live." This is a huge amount of extra work for functionality we had in Outbound already.