Skip to main content

Exporting Hyperion Planning artifacts using Shared Services

If you have made a Hyperion Planning application you can migrate the definition of any of the artifacts (dimensions, rules, variables, composite forms) you may have created.

Open the application from the applications' list. This lists all the major categories of artifacts. Click on 'Global Artifacts'. This shows the artifacts I mentioned above and which are of interest to us.

Each of the artifacts further act as subcategories, e.g. under Common Dimensions we have Attribute Dimensions and Standard Dimensions. 'Composite Forms' lists the forms according to their folders.

You can select all the artifacts you want to 'migrate' and click on 'Define Migration button. I selected the Composite Forms.
A popup will ask you if you want to include dependent dimensions. I checked the checkbox and all the dimensions which were used in those composite forms were also migrated. If you don't want the dimensions, don't select it.

Next screen asks you if you want to migrate the artifact to some other application or save the artifact definition in form of XML. I chose to save the file and gave 'exim' as the destination directory. The migrated XMLs were saved in : C:\Hyperion\common\import_export\admin@Native Directory\exim\resource\Global Artifacts

Final screen shows you migration summary. Click on Execute Migration button to start migration. A popup shows you button to launch Migration Status Report.

If the status is active, click on refresh button to get the latest status. If it is success, your migration has succeeded.

Isn't it too simple!


ashwin said…
सुझाव का धन्यवाद, आशा करता हु आगे भी ऐसा ही सहयोग मिलता रहेगा !

Popular posts from this blog

File upload problem: UTF-8 encoding not honored when form has multipart/form-data

The problem that I was facing was something like this. I was using Apache Commons File Upload library to upload and download some file.

I had a form in which user can upload a file and another field 'name' in which she can give any name to the file being loaded.

When I submitted the form, the file was uploaded fine but the value in name field was garbled. I followed all the possible suggestions I found:

<%@page pageEncoding="UTF-8"%> set. <%@page contentType="text/html;charset=UTF-8"%gt; set after the first directive. <meta equiv="Content-Type" content="text/html;charset=UTF-8"> in the head. enctype="multipart/form-data" attribute in the form. accept-charset="UTF-8" attribute in the form.
in the Servlet:
before doing any operations on request object: request.setCharacterEncoding("UTF-8"); For accessing the value

FileItem item = (FileItem);

if (item.isFormField()) {

//For regular…

java.lang.IllegalArgumentException: Malformed \uxxxx encoding

I was getting this exception during build while running ant. Googling didn't help much and I was flummoxed because the same code was running fine till now.

My code reads a text file and does some operations on the basis of values read. It was only when I saw the text files I understood the error. I had copied the text in wordpad and saved it as .txt file. Wordpad had put lot of formatting information before and after the content. Also there was "\par" after every line, which was giving this error.

So moral of the story: if you get this exception check your properties file (or any other file that your code might be reading.)

How to upload to Google Cloud Storage buckets using CURL

Signed URLs are pretty nifty feature given by Google Cloud Platform to let anyone access your cloud storage (bucket or any file in the bucket) without need to sign in.

Official documentation gives step by step details as to how to read/write to the bucket using gsutil or through a program. This article will tell you how to upload a file to the bucket using curl so that any client which doesn't have cloud SDK installed can do this using a simple script. This command creates a signed PUT URL for your bucket. gsutil signurl -c 'text/plain' -m PUT serviceAccount.json gs://test_bucket_location
Here is my URL:…