Issue with Grid POV

Hi ,
We have a report where in the GRid pov, we have set 3 dimensions as 'User Point of View" and others locked for a specific member..
We recently migrated from V7 to V11 and we are running into a issue where the lock on the dimensions goes away and all the dimensions are set to 'user Point of view"...Is there a way to fix this?
For Ex:
I have a dimension called "Scenario" set to 'Actual" and it is locked..
but when I run the report , it brings it up as a User POV...

When you right click on the Grid setup and click "Grid Point of View" does it show "Actual" grayed out?

Similar Messages

Issue with exporting Financial Report in Smartview 11.1.2.2

If I export a FR in "Export in query Mode" , it concatenates the parent with the child (parent.child) and does not return anything in Smartview. Even though the report works fine in workspace.
I narrowed down the issue and it seems if I use Stored member roll up instead of using Shared member roll up it returns the right data when I export the report in Smartview.
So the issue is only with the FR using Shared members.
Does anyone know if this is a known issue or can replicate this in their environment ? We are on version 11.1.2.2
Thanks

Nope that didn't work, but I figured out the error. I was running the command on a client machine. When I run the command on the server itself, it works fine.. well, now I have issues with my POVs, but at least it's finding my .csc file.
Thanks for your help John.

Issue with ALV grid print preview/spool

Hello everyone,
I am working on a report and I am having some issues with ALV grid. Currently in our DEV and QA environments the user can run the report, view the ALV grid, and print the grid without any issues.
However this isn't the case in the Prod environment. The user is able to run the report and view the grid without any issues. But when they click print preview or click print, the spool is incorrect. It shows the proper values from the grid, but the first field is reduced in length. Rather than showing a numeric field of length 10 it shows 99999999# or 99999999...
The programs are identical through every environment, including user parameters, formats, and spool settings. I have been told printing grids may have some issues, does anyone have any advice or dealt with this issue before?
I appreciate the help.
Thanks,
C

I was waiting to hear from the functional team on the matter and no one has mentioned any more issues. I am assuming the problem is solved. I just noticed the thread was still un-answered and wanted to give an update.
Thank you for you help Vijay.
Regards
C

FR Studio - Is there a workaround for the issue with referencing data from a grid with a different DB connection and different # of dimensions?

Hi,
I am trying to reference a column in a different grid with a different database connection. I did some research in the forums, and it seems like this is a known issue with FR Studio. The issue is that if the 2 different database connections have different # of dimensions, then the reference will throw an error.
For example, what I'm trying to do is below:
In grid2.column[A], I have the following formula:
grid1.column[A]
The result is an error.
The ultimate goal is to have a basic variance formula in the grid between grid1 and grid2, which have different database connections with a different # of dimensions. Is there a workaround at all to this bug? The example of the basic formula is below:
grid1.column[A] - grid2.column[A]
Any help is much appreciated!
Thanks,
Tiffany

Thanks for the detailed response Mike.
The issue with trying it in Grid1 vs Grid2 is that Grid1's DB connection has more dimensions than Grid2's DB connection. I can't change the DB connection to a database with more dimensions because you have to be able to map all dimensions from the existing DB connection (Grid1) to the new DB connection (Grid2). This isn't possible, so instead I have to map Grid2 (less dimensions) to Grid1 (more dimensions). It just ignores the extra dimensions from Grid1. Does that make sense?
Thanks again for your responses. It's very much appreciated.
Tiffany

The number of POV to be set exceeds grid POV

Hi All,
In smart view i am getting the below error.
The number of POV to be set exceeds grid POV.
Can you please let me know where i have change the number of POV value?
Thanks,
Prathap

Hi Prathap,
Are you using 11.1.2.1 Smart View? If yes, are you getting this issue while refreshing ??
If that is the case then go with 11.1.2.1.102.
http://john-goodwin.blogspot.com/2011/09/get-up-and-running-with-smartview.html
Cheers.!!!

Issue with "unknown user type 6" on Coherence 3.5.2

Having an issue with a cluster which is running using an internally developed cluster starter tool. This tool, and the associated cluster, all use POF, and upon attempting to connect a non-storing member to the cluster from java, the following exception is raised...
2011-07-11 15:54:58.338/2.469 Oracle Coherence GE 3.5.2/463p2 <Error> (thread=Cluster, member=n/a): This cluster node is
configured to use serializer com.tangosol.io.pof.ConfigurablePofContext {location=application-pof-config.xml}, which ap
pears to be different from the serializer used by Member(Id=1, Timestamp=2011-07-11 15:34:30.779, Address=10.74.82.193:8
088, MachineId=11188, Location=site:INTRANET.BARCAPINT.COM,machine:ldnpsm020006423,process:80976,member:ldnpsm020006423:
cacheserver:1).
java.io.StreamCorruptedException: unknown user type: 6
at com.tangosol.io.pof.PofBufferReader.readAsObject(PofBufferReader.java:3289)
at com.tangosol.io.pof.PofBufferReader.readObject(PofBufferReader.java:2600)
at com.tangosol.io.pof.ConfigurablePofContext.deserialize(ConfigurablePofContext.java:348)
at com.tangosol.coherence.component.util.daemon.queueProcessor.Service.readObject(Service.CDB:4)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid$ServiceConfigMap.readObject(Grid.CDB
:1)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid$MemberConfigResponse.read(Grid.CDB:1
3)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.onNotify(Grid.CDB:123)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.ClusterService.onNotify(ClusterServi
ce.CDB:3)
at com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:42)
at java.lang.Thread.run(Thread.java:619)
There is no serialiser configured in the cache config, instead we just set tangosol.pof.enabled=true, and set the pof config file to what is seen above. The thing which is very confusing about this error is that unlike other clients which we connect, and in fact the servers they connect to, this client never attempts to load the cache configuration file. The point at which this should happen, prior to pof loading, shows:
2011-07-11 15:54:57.260/1.391 Oracle Coherence GE 3.5.2/463p2 <Info> (thread=Main Thread, member=n/a): Loaded cache conf
iguration from "jar:file:/C:/Program%20Files/Oracle/coherence/3.5.2b463P2/lib/coherence.jar!/reports/report-group.xml"
I have tried every combination of classpath entries I can think of, and no matter what, it never shows an attempt to load the application-cache-config.xml supplied in the startup. Does anyone have any experience with something like this?

I guess your non-storing JAVA code does not specify -Dtangosol.pof.enabled=true and the -Dtangosol.pof.config =<POF file location> on joining the cluster. Post the startup java command and the complete logs.
If application-cache-config is not loaded then coherence-cache-config.xml should be loaded by default and set -Dtangosol.coherence.cacheconfig=<application-cache-config>
Cheers,
NJ

Photoshop CS4 Issues with the NVIDIA GeForce 8800?

I have an Mac Pro Intel 2 x 2.8 GHz Quad-Core Xeon with 6GB RAM running OS X 10.5.5 and an NVIDIA GeForce 8800 GT driving two monitors.
I just installed Adobe Photoshop CS4 fresh from a factory CD.
When I perform a Distort -> Lens Correction or do a Free Transform to rotate an image an arbitrary amount, and then follow that with a resize (tried 133% and 166%), the image ends up with a pattern of gray plaid overlaid -- especially visible in the darkest shadows. The pattern appears only on the rotated layers of an image.
This pattern persists if I quit and restart Photoshop, BUT -- there's no pattern visible if I open the same image in Photoshop CS3. It only appears in CS4.
This is easy to reproduce -- I just tried it with an image I created in Photoshop at 5x7" at 240dpi and filled with solid black.
I dropped a Bug Report to Adobe, and they wrote back suggesting "This is most likely an issue with your video card driver."
Anybody else out there having this issue? Anyone with an identical setup want to test this?
-=-Joe

sako75 wrote:
I'm seeing what you are talking about when viewing at 200% and up on my 300dpi images. I'm thinking that its the new pixel grid overlay for dialing in the details on the image.
No, that's not it. I can see it at 100%, and only on images that have been rotated and resized.
In fact, yesterday I rotated one layer under an unrotated layer, and only the rotated layer showed the plaid pattern.
And it's not a simple grid -- it's a real plaid-like gray, almost like stretch marks.
-=-Joe

Major Issues with views in A3

I am having some major issues with views in A3.
If you look at my screenshot I am in the Browser;GRID view, however many of my images are out of view to the right (should be 26). There is no way to see them or select them. Also note that there is no SIZE control on the bottom right!
If i view it in LIST mode, all my images show up. If I go to FULL SCREEN everything works like it is suppose to. It just happens in
http://farm5.static.flickr.com/4007/4354751139647d87b323b.jpg
Any ideas on how I can fix this?

If I go into split view, I do not get any scroll bars so there is no way of viewing all my images.

Issues with Custom Package in Lightroom 3...please help

I am having issues with the custom package in lightroom 3. I am selecting diferent cell sizes (with different aspect ratios) and placing multiple images in these cells.
On screen everything looks good, but when it actually prints some of these cells are coming out stretched!! For example, the 6x4 cell comes out fine (same aspect ratio as the original capture), but i have 2 x 1.5 inch cell whose image comes out stretched??
The first thing I thought of was the "zoom to fit" option, but this is not present in picture package.
Then I thought it perhaps it was something to do with the my print settins, but cannot find anything there.

I am having the same issue. I used a Matt Kloskowski print grid and when I printed it, or printed to file, some of the images in the 15 that were created in the template were distorted. Some the faces became wider and some narrower. Not just zoomed to fit. On screen it all looks correct. Many others on the forum where the template was posted don't seem to have this issue. I created a template myself just in case that was it but I got the same problem as walenahs. I tried to figure out what he had done but I didn't get it.
I have attached the two images. You can see the distortion in the second image on the top row (too narrow), and on the second row, the second in and second down, black and white (too wide).
Thanks

Screen Resolution issue - BDC Grid

Hi All,
I am facing an issue with BDC for PRMM transaction.
If we look at the PRMM transaction, the very first screen consist of GRid forAction type.
The records in the grid of PRMM transaction is changing as per the screen resolution of User desktop.
Example: In my screen, I am able to see 16 rows in Grid and in user desktop i can see 10 or 20 rows. Because of this the Pagedown option and BDC is not behaving properly.
Please suggest what should be done to resolve it.
Thanks,
Shilpa

Hi Shilpa,
during recording from SHDB, use check box for Default Size.
in call transaction syntax: use
data: wa_opt type ctu_params.
wa_opt-dismode = w_mode. [N OR A OR E]
wa_opt-defsize = c_check.[X]
wa_opt-updmode = 'A'.
CALL TRANSACTION c_me41 USING i_bdcdata
OPTIONS FROM wa_opt [INSTEAD OF HARD CODING MODE]
MESSAGES INTO i_msgcoll.
Hope this can solve your problems.
Regards,
Tutun

Click issue with s:Datagrid on mobile for iPads with retina displays (only left half is clickable)

I'm currently testing a Flex mobile application (that was originally made for iPad 2) on high rest iPad fourth generation and iPad Air devices.
I'm having this strange issue where the s:DataGrid, no matter where I use it in the application, will display correctly, but only the left half is clickable to select rows. The number of columns in the DataGrid is not important, nor is the width of the DataGrid, the problem is always present. As soon as you try to click in the right half, it doesn't work.
The application uses an applicationDPI of 160, and scales properly on the higher resolution devices.
So this feels like a bug to me, as if the DataGrid scales properly, but not it's clickable area?
I have tried a bunch of stuff to see if I could work around this issue, like calling invalidate functions and setting the DataGrid's width dynamically, but no change so far.
At this point I'm open for any suggestions or ideas...
Edit: After further testing it seems the same is true for the height. I noticed when I added more rows in the grid. Only the top half of the DataGrid can be clicked. So it really looks like a dimension issue with the clickable area?
Thanks

I ended up not using the DataGrid, and decided to use the experimental MobileGrid instead, which is not afflicted with this issue.
So this issue no longer concerns me.
BTW the default theme of MobileGrid is dark, but can be lightened up with CSS and by extending the MobileGrid skins, up to a point where I almost can't tell the difference v.s. the DataGrid.
It also performs better then the DataGrid. since it's based on List. With 300 elements, it scrolled noticeably faster.

Several issues with 2.4

There are a few issues I'm having with the 2.4 update. First, I just imported a bunch of shots. Now, on my second monitor, I'm in Loupe mode. The preview is pixelated. When I zoom up the image on the main monitor, it's just fine. This was not LR's behavior with 2.3 - the image looked the same when zoomed to 1:1 on both monitors. What's up with this?
Second, why hasn't Grid mode on 2nd monitor been fixed? I choose a dozen images in Grid mode on second monitor and add a keyword only to have that keyword applied to one image. This has been a bug/feature ever since LR started to support dual monitors. When, if ever, will this very annoying issue get fixed?
Third, after I edit an image in a external editor and then return to LR Grid mode, LR *insists* on changing my sort order. No matter what I do to keep sort order as "File Name," it keeps changing it to "Capture Time" or "Added Order." This has to stop. How?
Thanks.
Antonio

dpick2 wrote:
With 2.4, I am now having issues with keywords and captions only being applied to one photo even though many are selected. This is on my Dell Laptop running Xp.
This was not the case with 2.3.
Check that Library/Menu/Metadata/Show Metadata Only for Target Photo is NOT checked! Also that you are in Griid mode and selected multiples in the Grid.
Don

TS3276 I have issues with mail unexpectedly quitting, any suggestions?

Has anyone ever had issues with mail and/or Safari "unexpectedly quitting" repeatedly and the only thing that seems to temporarily fix it is to restart the computer?

Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
Step 1
Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select
View ▹ Show Log List
from the menu bar.
Enter the name of the crashed application or process in the Filter text field. Select the messages from the time of the last crash, if any. Copy them to the Clipboard (command-C). Paste into a reply to this message (command-V).
When posting a log extract, be selective. In most cases, a few dozen lines are more than enough.
Please do not indiscriminately dump thousands of lines from the log into this discussion.
Important: Some private information, such as your name, may appear in the log. Anonymize before posting.
Step 2
Still in the Console window, look under User Diagnostic Reports for crash reports related to the process. The report name starts with the name of the crashed process, and ends with ".crash". Select the most recent report and post the entire contents — again, the text, not a screenshot. In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.) Please don’t post shutdownStall, spin, or hang logs — they're very long and not helpful.

Selection issue with editable Spark DataGrid

Hi everyone,
I am evaluating the new Spark DataGrid and I'm having a very strange issue with the behavior of selection in an editable instance.
Here is my test application: http://www.playcalliope.com/flex/DataGridSelectionIssue.html (code here: https://gist.github.com/1129160)
And here are the steps to reproduce the issue:
select the very first cell at the top-left corner of the grid (the one with "Gabriele");
click on it once more, the editor appears;
now click on the cell just to the right of it (the one with "Genta").
You should see that editing ends as it supposed to do, but selection is placed on the third cell (the one with a 5 in it) instead on the one you clicked on. Playing a little with the grid you should see that this isn't the only case, but selection is really behaving randomly.
I am using SDK 4.5.1.21328.
I think this is a very basic usage case.. I can't believe this is not working properly, what am I missing?
Thanks a lot,
Gabriele Genta
Message was edited to add live example

Your running into a known bug, https://bugs.adobe.com/jira/browse/SDK-30088.
The bug will be fixed in the Mega release. To work around the bug you can create a custom editor and remove the "dataGrid.validateNow();" call in DataGridEditor.save().
Here's how I modified your example to workaround the bug:
<?xml version="1.0" encoding="utf-8"?>
<s:Application xmlns:fx="http://ns.adobe.com/mxml/2009"
               xmlns:s="library://ns.adobe.com/flex/spark"
               xmlns:mx="library://ns.adobe.com/flex/mx"
               minWidth="955" minHeight="600"
               backgroundColor="#E7E7E7"
               creationComplete="application1_creationCompleteHandler(event)">
    <s:layout>
        <s:HorizontalLayout horizontalAlign="center" verticalAlign="middle"/>
    </s:layout>
    <fx:Script>
        <![CDATA[
            import mx.collections.XMLListCollection;
            import mx.events.FlexEvent;
            protected function application1_creationCompleteHandler(event:FlexEvent):void
                testGrid.dataProvider = new XMLListCollection(testData.item);
        ]]>
    </fx:Script>
    <fx:Declarations>
        <fx:XML id="testData" xmlns="">
            <items>
                <item>
                    <id>1</id>
                    <cognome>Gabriele</cognome>
                    <nome>Genta</nome>
                    <uhm>5</uhm>
                    <bene>molto</bene>
                </item>
                <item>
                    <id>10</id>
                    <cognome>Pinco</cognome>
                    <nome>Pallino</nome>
                    <uhm>10</uhm>
                    <bene>poco</bene>
                </item>
            </items>
        </fx:XML>
        <fx:Component className="MyDefaultEditor">
            <s:DefaultGridItemEditor>
                <fx:Script>
                    <![CDATA[
                        import mx.collections.ICollectionView;
                        import mx.collections.ISort;
                        override public function save():Boolean
                            if (!validate())
                                return false;
                            var newData:Object = value;
                            var property:String = column.dataField;
                            var data:Object = data;
                            var typeInfo:String = "";
                            for each(var variable:XML in describeType(data).variable)
                                if (property == [email protected]())
                                    typeInfo = [email protected]();
                                    break;
                            if (typeInfo == "String")
                                if (!(newData is String))
                                    newData = newData.toString();
                            else if (typeInfo == "uint")
                                if (!(newData is uint))
                                    newData = uint(newData);
                            else if (typeInfo == "int")
                                if (!(newData is int))
                                    newData = int(newData);
                            else if (typeInfo == "Number")
                                if (!(newData is Number))
                                    newData = Number(newData);
                            else if (typeInfo == "Boolean")
                                if (!(newData is Boolean))
                                    var strNewData:String = newData.toString();
                                    if (strNewData)
                                        newData = (strNewData.toLowerCase() == "true") ? true : false;
                            if (property && data[property] !== newData)
                                // If the data is sorted, turn off the sort for the edited data.
                                var sort:ISort = null;
                                if (dataGrid.dataProvider is ICollectionView)
                                    var dataProvider:ICollectionView = ICollectionView(dataGrid.dataProvider);
                                    if (dataProvider.sort)
                                        sort = dataProvider.sort;
                                        dataProvider.sort = null;
                                var oldData:Object = data[property];
                                data[property] = newData;
                                dataGrid.dataProvider.itemUpdated(data, property, oldData, newData);
                                // Restore the sort. The data will not be sorted due to this change.
                                if (sort)
                                    ICollectionView(dataGrid.dataProvider).sort = sort;
                            return true;
                    ]]>
                </fx:Script>
            </s:DefaultGridItemEditor>
        </fx:Component>
    </fx:Declarations>
    <s:DataGrid id="testGrid" width="100%" height="100%"
                editable="true" selectionMode="singleCell"
                itemEditor="{new ClassFactory(MyDefaultEditor)}">
        <s:columns>
            <s:ArrayList>
                <s:GridColumn headerText="Prova" dataField="cognome"/>
                <s:GridColumn headerText="Prova1" dataField="nome"/>
                <s:GridColumn headerText="Prova3" dataField="uhm"/>
                <s:GridColumn headerText="Prova4" dataField="bene"/>
            </s:ArrayList>
        </s:columns>
    </s:DataGrid>
</s:Application>

Financial Reporting Studio - Grid POV

I have a report running from HFM (9.3.1.3.0.2176) using Financial Reporting Studio (9 9.3.1.0.0.0325) where I have restricted the Grid POV to 'Select members from a list' on Accounts.
When I run the report as an HTML from within Reporting Studio or workspace, a box appears entitled 'Preview user POV' with 'This report/book will run for the members on the user point of view listed below' with a selection box that when clicked only shows the accounts I defined in the list.
However, when the report is run from Workspace (9.1.1.0.0.248) by any other user then the accounts are not restricted.
Can I make the accounts restricted to the list for ONLY this report for all users without impacting any other reports and if so, please can you explain how?
Thanks in advance
PS I also restricted User POV in the vain hope that it would make a difference but no :-(

Select the grid. You will grid POV checked in right side properties window. Uncheck that.
Regards
Celvin
http://www.orahyplabs.com

Issue with Grid POV

Similar Messages

Maybe you are looking for