Skip to main content

Planning Web form not saving my data….

So I haven’t written to my blog since long and that’s just because I just did not find anything worthwhile all these days. Today I encountered a strange issue. So I thought to share with you guys.

We had a Planning web form set to input data. No Business Rules or calc scripts attached. Just an input form.

The issue : Every time any user enters the data into the form it says the data is saved but does not show up the data.

Causes: Probably one would think this might be a simple case of Implied Sharing or usage of a label only parent member with one of the single child only hierarchy in the form.. sure thing .. SO DID I!!
Its simpler than that!

Another weird behaviour: data is saved and reflects in the web form when I enter and submit through the Smart View Planning add-in

So what is the issue: the layout of the web form!
The data form was designed to check data values at CurrYr and NextYr. However the current year and next year were both set to the same value. In such a case when you enter the value in the current year intersection it just doesn't save. Now at this point I am not sure why but the strangest part is that if you enter that very same value under the NextYr column it reflects in both CurrYr and NextYr columns, so basically its just taking up the last value at the form. So either you need to remove the NextYr Column or set Next Yr to a different value to allow it to save through the web form properly.


In my case I did the latter and whoa!! Data saves now… Amazingly the same did not give me any trouble with saving data through Smart View. This issue is only specific to Planning. Now meanwhile when I am analyzing the strange behavior... do throw in your opinion guys.. J


Cheers!!

Anvi

Popular posts from this blog

Essbase for Beginners: Data Block concepts Part A

An Essbase outline has a number of dimensions.  The number of dimensions can range in quantity and size, but each dimension is identified as a dense or sparse dimension.  As we understood the concept of Dense and Sparse in our last discussion, let’s begin with the cocept of data blocks now. To understand this, let’s carry forward our hierarchy of 5 dimensions in a test application in my previous post.. We have 3 dense and 2 sparse dimensions each with 3 stored members. So let’s begin: Number of Existing Blocks = (potential number of blocks) * estimated density= 9 Block Size = Dense Stored * Dense Stored * Dense Stored * 8 bytes = 3*3*3 *8 = 216 Potential number of blocks = Sparse Stored * Sparse Stored = 9 If all dimensions are assigned as Dense, Number of Existing Blocks = (potential number of blocks) * estimated density= 1 Block Size = Dense Stored * Dense Stored * Dense Stored * 8 bytes = 3*3*3*3*3 *8 = 1944 Potential number of bloc...
Home

Shared Connection and Private Connection

You connect to data sources through shared or private connections. Shared Connections •Shared connections are stored in a central location and are available to multiple users through the Smart View Panel. You cannot add, edit, or rename shared connections, but you can save them as private connections, which you can edit and rename. Private Connections •Private connections are those that you create by saving a shared connection to your local computer or by entering a URL to a provider that is not configured for shared connections. When you create a private connection, it becomes the active connection. Shared Connections : 1. From the Smart View ribbon, click  Panel . 2. From Smart View Home or from the menu displayed when you click the arrow next to Home button, do one of the following: • Click a connection name under  Recently U sed . You can click    to pin items to this list. • Select  Shared Connections  to open th...
Home

Essbase for Beginners: Data Block concepts Part B

Below concepts involve Data Blocks in some way or the other, so to understand how Data Blocks behave it’s good to understand these concepts: Let's Begin!! Compression Clean and Dirty Blocks Fragmentation Restructure Compression: When Essbase stores blocks to disk, it can compress the data blocks using one of the following compression methods, this is based on the type of data that is being loaded into the Essbase database. Essbase provides several options for data compression: 1. Bitmap compression : This is the default compression method. Essbase stores only non-missing values and uses a bitmapping scheme. A bitmap uses one bit for each cell in the data block, whether the cell value is missing or non-missing. When a data block is not compressed, Essbase uses 8 bytes to store every non-missing cell. 2. Run-length encoding (RLE): Essbase compresses repetitive, consecutive values --any value that repeats three or more times consecutively, including...
Home