0
Category:
STATUS DETAILS

Comments

IGNORE THIS! You CAN do this. I has something setup incorrectly.

Category:

That would indeed be a good change!! very annoying now :(

Category:

I have voted. Our team would like to see an increase in the size of the segment query. At the moment we are having to work around the current 4,000 character limit, however, when we get into more complex segments this creates an issue. The current character limit hinders the segments we need to build, therefore, it is crucial that this is prioritised.

Category:

This is hilarious. How can you remove this from the client experience when it used to be there? This is going back to the RTC client, which was far superior to today's web BS. It just doesn't perform the same. Super users know it, MS apparently does not.So far, we're sticking with the last RTC client until the SaaS version gets real.

Category:

This Feature is must to show the right status to customer and refund status.

Category:

I would like to expand on this to say it would be nice if we could allocate space to each environment instead of having to spin up a pay as you go option to accomplish it. It is so risky to allow groups to use the Dataverse when it is pooled the way it is. We have had people run dataflows that took up over 400 GB of space. So for now we dropped the ability to use it.

Category:

this is really needed

Category:

It would also be helpful to send this in batch, all payments at once; currently it only allows one at a time.

Category:

Exactly what we need!

Category:

Very nice idea!!!!!

Category:

  • 1
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 500