I have two coumns with values, I need to get the columns 2 values separated by commas in the same line, is that possible in BO ?
Currently I have the ActionType values in mutiple lines of single Claim(WindowsDesc)
(Current:)
WindowsDesc ActionType
Claim1 AD
IQ
Claim2 AD
IQ
Claim3 IQ
NV
I am looking for the format: (expected)
WindowsDesc ActionType
Claim1 AD, IQ
Claim2 AD, IQ
Claim3 IQ, NV
Note: If the above tables are not clear, we can find these table in the attachment too
I dont know if it improves performance much, but you can utilise the reset_dim option in the previous function so that ‘Object 1’ does not get too big.
I’m fairly new to Webi and I’ve been trying to get this working and thought I’d had some success, but there are a few problem. I want a report that looks like:
Groups | Users | Auditors | No of Records
I want show the number of records per group/user with the Auditors being the comma separated list which is associated to a particular group.
I initially thought this was working but then I notice the count of No of Records was being multiplied by the number of auditors. Therefore I thought I need to bring this out into a separate query and combine the 2 queries in the report.
I thought I could jsut create a basic query of group/auditor to create the comma separated list. This seems to do what need, but would not let me add it into the original report. I think this is down to the fact that I need to same dimension in each query to get the merge dimension to work properly. However when I added in extra dimension the auditor column seem to throw back random results. Sometime it would not return anything, other times it seemed to return the same auditor multiple times. I’m not exactly clear what it doing and the function help in BOXI is pretty poor.
For the above solution, when the string length exceeds the pre-defined limit of 16387, it hits #OVERFLOW error. Is there any workaround to avoid this error?
Hi, this a longed-for and ingenious solution, props for that.
I am, however, facing the issue of it being too resource-heavy on the server. I am using it on a dimension which has around 3000 values.
I’ve found that unless I run it early in the morning, when there aren’t many users on, it drops the server. It takes about a gig of memory.
Have you observed something similar with this solution or does this happen only in our environment?
The interesting thing is that I’ve worked with a lot more complex reports, with multi-level sections, a number of chained variables that perform complicated calculations and on a lot more data. Sometimes the calculations can take 3-5 minutes but hell, they finish succesfully.
This solution, however, either runs in ~20 seconds or kills the server and everyone on it with about 3000 rows in the report.
It’s a pain to be so close to such a beautiful solution for a popular request, and yet find it to be unusable in its most absolute sense.
I hope someone can lavish mercy upon me (wink, wink Mak & Mark).