0
STATUS DETAILS

Comments

It would be ideal to be able to change the shape of a bubble based on a field. For instance map location of a service ticket one shape and the map location of a customer cold call visit another shape.

It would be ideal to be able to change the shape of a bubble based on a field. For instance map location of a service ticket one shape and the map location of a customer cold call visit another shape.

Please can we extend the multiple sorting of columns to the matrix visual and also include the ability to hide columns as well

The problem I've encountered is with having different clients using our reports. if the slicer has a value or (Blank) selected then the report doesn't work for most clients. It would be great for the slicer to select by default the first available option alphabetically (or however the data is sorted)

Is it possible this idea is more than 5 years old and still not implemented? wtf

BW on 6/12/2019 2:59:49 AM


Coming up to 3 years now since request and the only feedback we get is:


Administrator on 7/22/2022 8:30:06 AM
This request is on our roadmap


The date also has been updated on this Administrator post but the text hasn't changed? I guess 3 years development for a standard feature is fine for a billion dollar business Microsoft.






"Feature has been released in public preview."


How do I use it????

Thanks for this Matt - I'm on your email list so it was a great prompt / call to action! I'll ask my colleagues to support it too,

I'm not able to fully test functionality involving matrixes because selecting data while the drill-down option is enabled does not cause it to highlight elsewhere on the report. Uploading to the service is really slow and inconvenient in my organization for testing such functionality.

DG 11Aug2022 - Need team guidance on how to escalate the dissatisfaction with Vertex.
DG 15Aug22 - Namita sent a message to Dustin (and Rob cced) last week. Vertex improvement in the works.

Here is the comment from Jeff Anderson:

Assuming the backward compatibility issue mentioned is related to the retail packaging model, with their August release they have now moved to the new packaging model. So backward compatibility (for that area at least) should be less of an issue going forward.

Do they have a direct contact at vertex (technical account manager or similar) who is their direct contact? And do they similarly have trouble getting that person to pick up the phone?

Again I’m looking here for what concretely we can do to help. In conversation with their release manager, we let them know that we have a set of vocal customers who are unhappy and putting pressure on Microsoft, and let them know that list of customers. Short of continuing to tell them “customers are unhappy”, are there specific things you can think of that we can do to help?