Blank attribute

[iolaper]

I was trying to create a 'blank attribute' to put on my report. This column would have no data what so ever on it so that when users export it to excel they will have blank a blank column where they can write their own comments.
I dont want to create a blank column in my database and don't wanna use a metric as this column is between two other attributes.

I know this is freaky but would be great to solve!!

 

[nlim]

How about a "blank" attribute form, and make sure both are added on the template?

 

[iolaper]

Now, how do you create a blank attribute form?
There is no scope of creating the blank attribute without using a column from the database and I do not want to create a blank column.
So far what I have figured out is that if I use Applysimple(null,0,0) it will create a null field.
However I am looking for other options too!

 

[entaroadun]

Hmm... This is a good one. Have you tried using the Applysimple NULL yet? Does it really work? The engine will put NULL in the GROUP BY clause. Will that work?

Also, for MSTR to use the attribute properly, you have to attach your expression to a logical table. However, let's say you attach it to Table A and the report you are using this in doesn't have Table A. It will probably join across to Table A to get the NULL expression. You could attach it to all tables, but this would really mess with your data model.

Because attribute forms have to be attached to existing logical tables, you will have to create a dummy table. Oracle has such a table already called DUAL. You can pull DUAL into your schema, rename it Dummy or something like that, and attach an ApplySimple NULL expression to it. That way, whenever you use the blank attribute, the SQL engine will CROSS JOIN over to DUAL, which has one row. This won't disrupt the rest of your model. I'm not sure if SQL Server has the same.

However, this doesn't answer the question of whether or not you can GROUP BY NULL.

 

[iolaper]

ahem...okkkkkkkkkkkkkkk...that was some explaination!!
I needed it on one report only and I have created the applysimple NULL attribute and made it a 1-1 relation to the ID it will relate to. Guess it works fine!