Forum

Data composition schema condition

Apr 11, 2012 04:14 AM

Interested

Points:: 15
Joined:: Oct 27, 2011

I could make two different queries fro the report:
include condition to virtual table

Code

SEL ECT
   ContabilidadTurnovers.ValorTurnover,
   ContabilidadTurnovers.CantidadTurnover,
   ContabilidadTurnovers.Empresa,
   ContabilidadTurnovers.ExtDimension1
FR OM
   AccountingRegister.Contabilidad.Turnovers(, , , Account = &SlaesAccount, , Empresa = &Empresa, , ) 
   AS ContabilidadTurnovers

or just use a filter in data composition schema for filtering Empresa.

The first option should work faster, but it have a problem if the Empresa parameter is not defined - the query ended with an error. The second one is more versatile and give us more options. Are there any optimizations which make use of second method as effective as the first one. And how is recommendable?

Profile

Timofey Bugaevsky	#2 Apr 11, 2012 09:55 AM
Guest Points:: Joined::	Virtual table parameters will work faster. To optimize your report you should set it when work with large amount of data. If the data is not that large you can use more versalite mechanisms to provide more flexibility.
	Profile

Users browsing this topic (guests: 1, registered: 0, hidden: 0)