Product ideas | Community
Skip to main content

10000 Ideas

JarnoRossiLux2New Participant

Sharing with User Group instead of Product ProfileNew

Hi all, I think this is one of the critial issue every one has with the Adobe Analytics credential system. We use “product profile” for sharing workspace because Adobe shows “product profile” instead of “user group” in the box selection for sharing assets. That makes absolutely no sense and it’s not correct from a credential-strategy point of view.I need to share a report with a TEAM (user group), no with a CREDENTIAL SETTINGS SETS (product profile). We need to immeditalety bring to engineer/architect or product manager this point.We need this change now in Adobe Analytics. Companies with hundreds of users share reports every hour. Can you image how much "mess" and redundant settings we are accumulating in our account hour by hour just because of this credentials wierd behaviour? At the moment Adobe Analytics brings us to create additional product profile when we need to share reports with a group of users. In that product profile settings we also have to grant access to all report suites involved in workspaces we want to share (can you image the workload to keep everything aligned?!?!?!) (bytheway this is another unexpected recent news for credential point of view).  You dont agree with my idea yet? Ok, listen to this: when users try to share any report, they can see in the box of user selection not just the list of other users, but also all the product profiles!!! ...do we want to share with the folk all our admin stuff??!! 

AnmolGu1New Participant

Urgent: Request for Currency Calculation Enhancement in WorkfrontNew

Description - Workfront should perform calculations based on "Currency" field for an issue. For instance, if the "Currency" field is populated with GBP, the system should treat it as GBP and reflect currency values accordingly, instead of relying on the project's default currency. Currently, if a project’s default currency is set to Euros due to the first issue added with lets say Euros currency, any subsequent issues, even if in a different currency like GBP, will still reflect in Euros. This leads to incorrect currency symbols and values being displayed. Why is this feature important to you - This feature is critical because it ensures the accuracy of financial data in Workfront. Incorrect currency representation can lead to misinterpretation of financials, impacting decision-making and reporting. Having the ability to reflect the actual currency based on the specific "Currency" field is essential for accurate project tracking and financial integrity. How would you like the feature to work -The system should either:Use the specified "Currency" field to determine and reflect the correct currency symbol and values, orConvert the currency based on exchange rates when a different currency is used, and then reflect the converted value in the project’s default currency.Current Behaviour - Currently, Workfront relies on the project’s default currency for all issues, even when a different currency is specified in the "Currency" field. This results in incorrect currency symbols and values being displayed, leading to potential errors in financial reporting. We've discussed this with the Workfront support team(Whittney Clark), who acknowledged it as an issue and suggested it as an enhancement. Immediate attention to this issue is necessary to avoid further inaccuracies. Let me know if you need any additional information from my end.

MikeCo9Employee

Expose the Adobe Analytics Data Dictionary in the Adobe Analytics API - Feature RequestNew

PLEASE UPVOTE THIS IF YOU NEED IT.A few months ago, Adobe added a new feature to Analysis Workspace that exposed a data dictionary.https://experienceleague.adobe.com/docs/analytics/analyze/analysis-workspace/components/data-dictionary/data-dictionary-overview.html?lang=en We use the Analytics API often and would like to have the Data Dictionary data exposed in the Analytics API. Currently, the data in the data dictionary is unavailable to the API. Extracting this data would be valuable for documentation and internal reporting.  By exposing the Data Dictionary data in the AA API, we can streamline the governance of our data collection components and report on relationships between components. (components typically used with selected components) We will also be able to perform the following programmatically:Identify duplicate components that need to be consolidated.Identify components that aren’t collecting any data so they can be either updated or deleted.Identify components that are not yet approved.Update component descriptions directly in Adobe Analysis API so that any updates made to the component descriptions in the Data Dictionary are reflected in the Report Suite. We want AA API access to the following:Component Type, Description, Approved/Unapproved, Frequently Used With, Similar To, Tags. Thank you for your consideration