Other ideas/suggestions

One of my partners, Exakis, shared with the an improvement Idea for FPX (soon MPX). He said that when they export the Opportunities in an Excel file, the CPOR eligibility column does not exist, as it is in the Table view (before export). Instead, they have 2 columns: Claim ID and Claimed by Others (True/False). When the Claim ID is referenced- this means the partner has already a CPOR claim on that tenant. When the Claim ID is blank and the Claimed by Others shows “True”, it means there is a claim submitted by another partner. But When the Claim ID is blank, and Claimed by Others  shows “False”, in theory, there is a CPOR opportunity for the partner but additional verifications should be done by them to see if they can proceed with the CPOR claim. It can be that some workloads do not exist as they are mentioned in the Opportunities, to be further claimed. Example: DNR P1+P2, MIP P1+ P2, DLM P1+P2, etc. So it is not straight forward for them to identity a CPOR opportunity,Their ask is to have the same information/column in the Excel file export, CPOR eligibility (Yes/No).

Currently a user can filter the MPX data insights based on MCI eligibility being Yes or No. This is useful, however to improve targeting when partners are looking to drive a specific campaign it would be useful if they could have a more granular level of filtering on the MCI eligibility. For example, if the partner is looking to target Data Security as part of a wider AI readiness campaign, they may wish to filter the MPX data to see only customers who are eligible for the Data Security engagements. 

LXP Dashboard(Opportunities)で実態として該当しない顧客がオポチュニティとして表示されるため、SKUの判定ロジックを見直し、正しいSKUで扱われるように変えて欲しい。例) 既にME5をお持ちのお客様のSKUがO365と扱われているケースがあります。 Since customers who do not actually fall under this category are displayed as opportunities, I would like to see the SKU judgment logic reviewed and changed so that it is handled with the correct SKU.For example, there are cases where customers who already have ME5 have SKUs that are treated as O365.