Error In Grid Xml Hyperion
Technology and Trends Enterprise Architecture and EAI ERP Hardware IT Management and Strategy Java Knowledge Management Linux Networking Oracle PeopleSoft Project and Portfolio Management SAP SCM Security Siebel Storage UNIX Visual Basic Web Design and Development Windows < Back CHOOSE A DISCUSSION GROUP Research Directory TOPICS Database Hardware Networking SAP Security Web Design MEMBERS Paul_Pedant DACREE MarkDeVries MacProTX Inside-ERP VoIP_News Inside-CRM maxwellarnold I_am_the_dragon PCMag Michael Meyers-Jouan TerryCurran Chris_Day Andrew.S.Baker JoeTorre bracke Locutus Ramnath.Awate Dennis Stevenson Craig Borysowich DukeGanote Richard mircea_luca AbhaiTripathi Nikki Klein knowscognosdoi Clinton Jones blrvenkat Iqbalyk bluesguyAZ59 COMPANIES CA, Inc. Epicor Software ... Compuware CloudLock View All Topics View All Members View All Companies Toolbox for IT Topics Oracle Groups Ask a New Question Oracle BI The Oracle BI group is for the discussion of technical issues that arise during the implementation, configuration, or daily use of Oracle Business Intelligence solutions. Home | Invite Peers | More Oracle Groups Your account is ready. You're now being signed in. Solve problems - It's Free Create your account in seconds E-mail address is taken If this is your account,sign in here Email address Username Between 5 and 30 characters. No spaces please The Profile Name is already in use Password Notify me of new activity in this group: Real Time Daily Never Keep me informed of the latest: White Papers Newsletter Jobs By clicking "Join Now", you agree to Toolbox for Technology terms of use, and have read and understand our privacy policy. Using Smartview in Excel for HFM and Encountering Error Tess Lee asked Apr 7, 2014 | Replies (2) We are using Smartview in Excel for HFM and encounter this error: " Error in grid xml: each dimension must be used once and only once.". Any idea how to fix it? Join this group Popular White Pa
score for this postmatthu from IP address 194.59.172.128I am using SmartView v11.1.2.5.210 Hyperion has a function called HypSetOption which can be used either to set a sheet option (by passing a sheetname) or to set a default option (by passing a "" sheetname). But this question is relevant whether or not you are using VBA. So, for example, sts = HypSetOption(HSV_MEMBER_DISPLAY, 0, "Sheet2") 'set display option to member only for sheet2 sts = HypSetOption(HSV_MEMBER_DISPLAY, 1, "") 'set default display option to name and http://oracle.ittoolbox.com/groups/technical-functional/oracle-bi-l/using-smartview-in-excel-for-hfm-and-encountering-error-5470844 description My experience is that I developed a sheet (using an ad hoc retrieval - actually HFM, but I suspect SV behaves identically?) and I did not specifically set a particular option to display Member Name Only but this is the option I could see displayed when I examined SV options via the Excel ribbon. Then I disconnected and distributed http://www.network54.com/Forum/58296/thread/1434034714/Best+practice+HypSetOption+sheet+options the sheet to several users. When one particular user looked at SV options they saw Member Name and Description instead of member Name only and this caused the retrieval to fail (Error in Grid XML: Each Dimension must be used once and only once). Possibly this was because they already had another workbook open? Can somebody please explain how this is meant to work? i.e. how can I save the options I am seeing as sheet options so they are re-used by another user who may have different default options? Thanks!Scoring disabled. You must be logged in to score posts.Respond to this messageAuthorReplyJeff McAhren63.108.38.204Just a commentNo score for this postJune 11 2015,4:23 PMSorry, I'm not going to be much help here, other than to commiserate with what you're experiencing. We have a fiscal pack report generator workbook that relies on many options being set to very specific settings to get the correct output. We've observed that sometimes setting options doesn't always work. Some work, but the same option needs to be set multiple times in the same stream of
its affiliates. Other names may be trademarks of their respective owners.This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your https://docs.oracle.com/cd/E17236_01/epm.1112/readme/sv_1112200_readme.html license agreement or allowed by law, you may not use, copy, reproduce, translate, http://docs.oracle.com/cd/E25178_01/doc.1111/e25450/hyperion.htm broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any error in errors, please report them to us in writing.If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:U.S. GOVERNMENT RIGHTS:Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific error in grid supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affi
chapter describes common problems that you might encounter when using Oracle Enterprise Performance Management and explains how to solve them. This chapter includes the following topics: Problems and Solutions for Foundation Services Problems and Solutions for Financial Reporting Problems and Solutions for Hyperion Provider Services Problems and Solutions for Essbase 3.1 Problems and Solutions for Foundation Services This section describes some common problems and solutions for Foundation Services. It contains the following topics: Getting Started with Logging Basics for Foundation Services Web Traffic Snooping EPM Registry Hyperion Security Username/Password Authentication Fails during Enterprise Scheduler Services Essbase Cube Creation in the Domain EPM Workspace Allocation Manager Smart View 3.1.1 Getting Started with Logging Basics for Foundation Services Log files are the best tools for analyzing what might be wrong with the system configuration. The logging configuration file, the defaults it ships with, and instructions for changing change those defaults will help with the analysis. Configuration: The logging.xml file in the following directories contains the loggers and their default levels: (UNIX) DOMAIN_HOME/servers/server_name/logs (Windows) DOMAIN_HOME\servers\server_name\logs The DOMAIN_HOME is named BIDomain. Output: The default locations of the loggers are rooted in the following directories: (UNIX) DOMAIN_HOME/servers/server_name/logs (Windows) DOMAIN_HOME\servers\server_name\logs These files include: /registry/registry.log /css/css.log /workspace/Framework.log /workspace/workspace.log /financialreporting/fr.log CalcManager.log Loggers: Increase or decrease the levels of these loggers: oracle.EPMCSS oracle.bi.bifndnepm.epmreg oracle.bi.bifndnepm.bpmui oracle.bi.bifndnepm.workspace oracle.EPMFR oracle.EPMAnnotations oracle.EPMJCR oracle.EPMADM oracle.bi.bifndnepm.calcmgr To change logger levels, perform the following steps: Go to Fusion Applications Control. From the navigation pane, expand the farm and then WebLogic Domain. Right-click a Managed Server from within the