Has anyone ever gotten an error message “Variables are not compatible”?
I have one user who does the following:
Creates a new query and report.
On the report, in an existing cell or in a newly inserted cell, double clicks to type text in the field. 3. Then gets the “Variables are not compatible” error message.
I have checked everything I can find, and this seems to happen randomly. She’ll be able to do this fine for some cells in the report and then has problems with others. I haven’t been able to find any pattern in these errors.
Has anyone ever gotten an error message “Variables are not compatible”?
I have seen a couple of occurences of this. I had a report once that would not let me change even text in any cell. I got round it by rebuilding the report from the beginning and thought it was perhaps caused by the report originally being a v3 report. However, since then a colleague had a similar problem and it was due to one object in the report not being used correctly. Is a synchronisation being done in affected queries at all?
<<Has anyone ever gotten an error message “Variables are not compatible”?>>
This happens when you have more than one query in the document. If you try to use unlinked dimension objects from a second query you will get this message. I found that if you redefine the variable as a detail object (Format/Variables/Add) you can add it to the report without a problem.
Barbara Rosen
Database Development & Admin Services
Salomon Smith Barney
Phone: (212) 723-2756
e-mail: barbara.rosen@ssmb.com
Has anyone ever gotten an error message “Variables are not
compatible”?
I have seen a couple of occurences of this. I had a report once that would
not let me change even text in any cell. I got round it by rebuilding the
report from the beginning and thought it was perhaps caused by the report
originally being a v3 report. However, since then a colleague had a similar
problem and it was due to one object in the report not being used correctly.
Is a synchronisation being done in affected queries at all?
Yes…there is a synchronization being done because of the contexts involved. Is there something with synchronization that causes this problem?
I think so. I can’t remember exactly when a synchronisation occurs now (can anyone help me here?). I seem to remember that we reported this issue to BO Support and they said the problem was being caused by a problem in our universe joins. We never actually changed anything though so I’m not sure if we’ve really solved the underlying problem (since it did go away when I rebuilt the main report that was affected).
One idea to try might be to remove objects from an affected query one at a time to try and work out if it can be narrowed down. This could be made easier by looking at the SQL and seeing which objects caused the synchronisation to occur (differences in the two SELECTs generated). Also try looking to see if there are any references to objects that have been deleted in the variables window and remove them.
Let me know if you have any success. Have you spoken to BO Support about this? If so, what did they say?
I have spoken to BO Support…they seem to think that it has something to do with the contexts and joins in our universe. We are going to look at changing and/or deleting many of the joins.
They also said that something weird is happening because with this synchronization and 2 queries, we should be getting 2 blocks of data back as a result set. It seems that we are only getting one back, so we can’t get all the data that we need.
I’ll let you know if they have any other good ideas. Amy Martel amartel@allmerica.com
Yes…there is a synchronization being done because of the contexts involved. Is there something with synchronization that causes this problem?
I think so. I can’t remember exactly when a synchronisation occurs now (can
anyone help me here?). I seem to remember that we reported this issue to BO
Support and they said the problem was being caused by a problem in our universe joins. We never actually changed anything though so I’m not sure if
we’ve really solved the underlying problem (since it did go away when I rebuilt the main report that was affected).
One idea to try might be to remove objects from an affected query one at a
time to try and work out if it can be narrowed down. This could be made easier by looking at the SQL and seeing which objects caused the synchronisation to occur (differences in the two SELECTs generated). Also
try looking to see if there are any references to objects that have been
deleted in the variables window and remove them.
Let me know if you have any success. Have you spoken to BO Support about
this? If so, what did they say?
In one data provider I have the variable . In the second data provider I have the variable . I need to do a calculation to figure the difference between the two dates in number of days.
I have used the DaysBetween function before on the same objects when they were in the same data provider. However, when I try it now, I get the error “Variables are not compatible”.
Does anyone have a suggestion as to how to use the DaysBetween function or another way?
In a message dated 00-03-13 14:27:26 EST, you write:
I have two data providers. They are linked on .
In one data provider I have the variable . In the second data provider I have the variable . I need to do a calculation to figure the difference between the two dates in number of days.
I have used the DaysBetween function before on the same objects when they were in the same data provider. However, when I try it now, I get the error “Variables are not compatible”.
Does anyone have a suggestion as to how to use the DaysBetween function or another way?
Susan:
I am betting that both Invoice Date and Required Date are dimension objects. That being the case, BusObj will not let you include them both in a block. Why?
Short version of the answer: Dimension objects are keys. Unlinked keys result in a cartesian product. Cartesian products are bad.
Short version of a solution:
Create a new variable called Local Invoice Date. Make this variable a Detail of Order Number.
The formula =
Repeat for Local Required Date.
Now that the objects are details instead of dimensions, you can use them in the same block. Once you get them in the same block, you should be able to use the DaysBetween() function.
Yes, both objects are dimensions.
I tried your suggestion, but still get the error message. I am able to show the objects in a column, but cannot do a calculation.
Stupid question, but are both dates defined as a) dates and b) in the same format? I have found some cases where the newer version of bo / webi handle dates more ‘accurately’ for lack of a better word… Things that worked under 4.15 / 2.02 don’t now, but the now is more correct.
If that makes ANY sense…
Brent
Dave:
Yes, both objects are dimensions.
I tried your suggestion, but still get the error message. I am able to show the objects in a column, but cannot do a calculation.
In a message dated 00-03-13 15:09:49 EST, you write:
Yes, both objects are dimensions.
I tried your suggestion, but still get the error message. I am able to show the objects in a column, but cannot do a calculation.
Any other suggestions?
Thanks.
Susan
Make sure that your block contains the DETAIL objects, not the dimensions. Then make sure that your formula for DaysBetween() uses the details as well.
A recap:
Create local detail copies of the dimensions Invoice Date and Required Date 2. Attach the details to the Order Number dimension from the appropriate data provider
Ensure that the Order Number dimension objects are “linked”. You can do that by reviewing the data in the View Data (Data Manager) window. Click on one of the Order Number objects… if you don’t see the Windows shortcut symbol (small arrow) then your objects are not linked. Click on the Definition tab, and link the two order number objects together. 4. Create a block with Order Number, Local Invoice Date, Local Required Date 5. Build a new variable, using the formula:
=DaysBetween(, )
That should work!
If you are still getting the message about being incompatible, I suspect you are either trying to go back and use the Dimension date objects instead of the detail copy, or your order numbers are not properly linked.
