Discussions
Categories
- 17.9K All Categories
- 3.4K Industry Applications
- 3.4K Intelligent Advisor
- 73 Insurance
- 537.3K On-Premises Infrastructure
- 138.6K Analytics Software
- 38.6K Application Development Software
- 6K Cloud Platform
- 109.6K Database Software
- 17.6K Enterprise Manager
- 8.8K Hardware
- 71.2K Infrastructure Software
- 105.3K Integration
- 41.6K Security Software
Patch .208 Update Smart View Data Grid Error at Parent currency for Top Entity Member
Hi
We have applied patch set .208 to our HFM DEV environment and now getting an error "An unexpected error occurred in the data grid object" when retrieving the Top Entity Member with Parent Currency intersection. Previously and in our production environment, the gird would just return #Invalid without this error. Is anyone experiencing the same issue or knows how to resolve it?
I've attached screenshots.
Many thanks.
Chris
Best Answer
-
Hi
This is a bug. Fix is planned in the upcoming PSU 11.1.2.4.209 patch
Chris
Answers
-
Have you tried with a new grid?
Also, check the smarview options.
-
Hi
Same issue in a new grid.
On same machine with same SV settings we get the error on Dev (updated with patch) but not Prod.
All users getting same error on Dev.
Chris
-
Please raise a SR with the details.
-
Hi
We have raised an SR. Oracle support going to test internally.
Anyone installed patch set .208 and can reproduce the error?
Chris
-
Hi
This is a bug. Fix is planned in the upcoming PSU 11.1.2.4.209 patch
Chris
-
Thanks for the update. Just FYI on this issue, any value dimension member above <Entity Curr Total> requires the entity to be written as Parent.Child format. The fact that Smart View returns one error or another is the bug you shared with us, but either way it's still an error. I just wanted readers to understand how to avoid the error in the first place.
- Chris
-
Hallo
1) Top entity member doesn’t have a parent.child relationship.
2) You can’t avoid not having the top entity member with parent currency in an ad-hoc grid where you are testing roll-ups i.e. all entities in rows and all value dimensions across columns.
3) What users need to understand is how test scripts miss this before release and why fixing issues with a patch set creates new issues.
Chris
-
When you have the invalid column in there, does the grid refresh all the other cells, or does this one bad column stop the whole refresh?
-
The whole grid doesn’t refresh.
Also, I’ve tested children without parent prefix and it returned #invalid without this error (as it should).
Only the Top Entity member results in pop-up error.
