Hide tablix and space issue

Question

Post reply

Hide tablix and space issue

PSB

SSChampion

Points: 13195
More actions
May 13, 2015 at 1:03 pm

#300632

Hi,
I have a report where I have two tablixes (A,B) with just images on them. I need to show tablix A when parameter value = A and hide tablix B and hide the space taken by tablix B as well.
I need to show tablix B when parameter value = B and hide tablix A and hide the space taken by tablix A as well.
This functionality works for me apart from hiding a Tablix doesn't shrink the space and move content after it up .
Please help .
Thanks,
PSB
Forum Etiquette: How to post Reporting Services problems

[/url]

Forum Etiquette: How to post data/code on a forum to get the best help - by Jeff Moden
[/url]

How to Post Performance Problems - by Gail Shaw
[/url]

PSB SSChampion Points: 13195 More actions · Answer 1

PSB

SSChampion

Points: 13195

May 13, 2015 at 1:36 pm

#1797662

Any help will be greatly appreciated .

mister.magoo SSC-Forever Points: 47174 More actions · Answer 2

Can you supply an example of a report that doesn't work?

I have many reports that hide parts at runtime and none fail to reclaim the space, so I wonder how exactly you have built it.

MM

select geometry::STGeomFromWKB(0x0106000000020000000103000000010000000B0000001000000000000840000000000000003DD8CCCCCCCCCC0840000000000000003DD8CCCCCCCCCC08408014AE47E17AFC3F040000000000104000CDCCCCCCCCEC3F9C999999999913408014AE47E17AFC3F9C99999999991340000000000000003D0000000000001440000000000000003D000000000000144000000000000000400400000000001040000000000000F03F100000000000084000000000000000401000000000000840000000000000003D0103000000010000000B000000000000000000143D000000000000003D009E99999999B93F000000000000003D009E99999999B93F8014AE47E17AFC3F400000000000F03F00CDCCCCCCCCEC3FA06666666666FE3F8014AE47E17AFC3FA06666666666FE3F000000000000003D1800000000000040000000000000003D18000000000000400000000000000040400000000000F03F000000000000F03F000000000000143D0000000000000040000000000000143D000000000000003D, 0);

PSB SSChampion Points: 13195 More actions · Answer 3

Hi,

Below is the sample DDL and attached is the rdl. When Order1 is the Order Number then Legend and Map1 should be displayed and table7 space should not be visible.

When Order2 is the Order Number then Map2 should be displayed in the space used table9 and table7 space should not be visible. I could not get this part working for Order2 in the Test report. But this is the main idea.

CREATE TABLE dbo.TestOrders

(

OrderNumber CHAR(25) NULL,

mapimage IMAGE NULL,

maplegendimage IMAGE NULL

)

INSERT INTO dbo.TestOrders

( OrderNumber ,

mapimage ,

maplegendimage

)

SELECT 'Order1' , -- OrderNumber - char(25)

0xFFD8FFE000104A46494600010100000100010000FF, -- mapimage - image

0xFFD8FFE000104A46494600010100000100010000FF -- maplegendimage - image

UNION

SELECT 'Order2' , -- OrderNumber - char(25)

0x89504E470D0A1A0A0000000D494844520000051C0, -- mapimage - image

NULL -- maplegendimage - image

SELECT * FROM dbo.TestOrders

mister.magoo SSC-Forever Points: 47174 More actions · Answer 4

Thanks, I think I see what you are trying to do, but the logic is flawed in the expressions that determine visibility and I am going to offer an alternative that is cleaner anyway.

Attached is a new version of the report that uses the database images (I used new ones because I couldn't get yours to display) for the maps and does it all with one tablix.

The new data is here :

truncate table Testorders;

go

INSERT INTO dbo.TestOrders

( OrderNumber ,

mapimage ,

maplegendimage

)

select 'Order1', 0x89504E470D0A1A0A0000000D49484452000001520000006D08020000007CEC7E74000000017352474200AECE1CE90000000467414D410000B18F0BFC6105000000097048597300000EC300000EC301C76FA8640000044349444154785EEDDB4B56DB480086D15E1EBD9EAC851574EF20871D846946C90A1864CC0A681EC62A3D4A2AB9B129F3DF7B6A44145B70F495AA64F8EB0908237B88237B88237B88237B88237B88237B88237B88237B88237B88237B88237B88237B88237B88237B88237B88237B88237B88237B88237B88237B88237B88237B88237B88237B88237B88237B88237B88237B88237B88237B88237B88237B88237B88237B88237B88237B88237B88237B88237B88237B8823FB533C7EBFFBE7EF7F5FC6B7DF8F87AFC1D5B88AEC1F7F7D7B6D6C323E2F39D973D5FACEFECFEFBB9B71EA4BE3C7CFC3E117F305B23F7E0B97FFE9F1E9FACDFEE176087B7B5C36BF2F90FDF1C72BFB407D663F5BD52FD4D572CCB95C7DF63FEF8F3F37D907EA31FBD17DFEE6FEE1F0E5450F3FCA5DC0EDEAB11FE79AB39F4E97B20FD45FF6E57EBE29AAD1757C998BF8FAB22F6EEF9321FB40DD653FDCEA6FEE7EFD397C71C3EE99A2D9BC96D705C58EEC979E4A7E4269B2A7D059F665247B56EC43870B93C5B01CB8FB7E8C74BCD69DFFAF7A27A3B192FDD6C71095DE4E3ADB4DB2A7D059F6C7AB73EF955D3456D4F2661AD2C26704E3B71B2691CD51CBBE6DD6584A6EF7D99E64782622FB407D655FACF0D79FE4CD15F7C3E932A108E9F67EF90E5C8634BE4BCF269171878BD98F5F61DA55F9AF0BDFE6CEB33D91ECA37595FD4ABADB861AA729162FFB3EE631BF2B0EAE4F3DAB7BFBE215AA5B80A2EDFADAE438EA677B32D947FB3AD917DBFB49AEE390D65FB96D97B196FDF00AAB0B96E33D7F7D92DAFF736823FB685D653F5C8B27DCDF5AB2DF7CD961C9B0DADB4AF6C757D87AAFF7B39ACE2F3BCEF67F907D34D9975A8FAC67FFFE2D346CBF0F1384ECB9B8AC45FE5648AD316C67BF678CDF4BF69C5DD623BD8D908EFBEDAD7B7535FBF133FCC6217B2EACABEC8B74D79F872D589932643F27FB687D657F995FD7A9FAC0ECF79EFF40F69C5D67D99777CB3DEBFC62633FEFAD3DA4D618B6F7F6B2A7639D65FF7C3D0EEBFCF672868B78D6E1B3F6905A8FAC67DFFE015E8DEC39BBEEB21FDDF09B76F84327958B784748C5AA61EDAD57B25F5D77B4903D67D75FF6E50DFF259EF5F28BFBFCF358DE17EC0969ED19C1BBF2CF6C161617C5296D4F5BCF074F8E913D67D763F6E5A57F180BFDCC8E5928F0CDBE904693CE641E99FF5DDDE29B4E0E5B3AA6FE9985EC39BB3EB37F31CA6F73549B7FB637A4F10A627DD4DE773E41D4C665B26F3E9F73CE35F4A2DFEC5F94FBFCFAD8BA5F9D1052BDFCD71DFBCADE7ED076F2A7FF96C12EB2A7D077F6074309A3B1BD737E736A4893548A47744DD91F544EBEFA1F65CFD95D45F6C047923DC4913DC4913DC4913DC4913DC4913DC4913DC4913DC4913DC4913DC4913DC4913DC4913DC4913DC4913DC4913DC4913DC4913DC4913DC4913DC4913DC4913DC4913DC4913DC4913DC4913DC4913DC4913DC4913DC4913DC4913DC4913DC4913DC4913DC4913DC4913DC4913DC4913DC4913DC4913D84797AFA0FC38A2430B64240110000000049454E44AE426082, 0xFFD8FFE000104A46494600010100000100010000FF union all

select 'Order2', 0x89504E470D0A1A0A0000000D49484452000001520000006D08020000007CEC7E74000000017352474200AECE1CE90000000467414D410000B18F0BFC6105000000097048597300000EC300000EC301C76FA8640000066E49444154785EEDDC3D4F1B491CC771FB5E8079A888CE409C124E484869EE28428B8553A4354D52722D5552932A2D94B9C6B4290E64DA440A5C836489609771E0F6145706FC067CBBF678778C77D7EB353663FEDF8F2C658C1233B1F637CFBBC966B3990020C92FEA4F0062107B401C620F8843EC0171883D200EB107C421F68038C41E1087D803E2107B401C620F8843EC0171883D200EB107C421F68038C41E1087D803E2107B401C620F8843EC0171883D200EB107C421F68038C41E1087D803E2107B401C620F8843EC0171883D200EB107C421F68038C41E1087D803E2107B401C620F8843EC0171883D200EB107C421F68038C41E1027D96C36551191358E8A7FEF5F3BA5A5D5971F9652AD1F0293622262DF28EF1C962AEA8DE7E12247EC31D1CC8E7DAD527C5DAA27D5BB2099DDFCDAAA2A8FC764C5DEABADAE99593FFE23ADDE401673636FED1F7C3E52E5FEC61BBF8988BD7FDAEF20FC229919FB9E51BD4FBAA2FC9D519988D8476D379B33AB7F6597E7D43B486062ECBBAED73EDD9175B2F1A5EACE02365F6C6D8FA3EB9AB0D8FB7C87DDDF9BC1FF0B8C82791B78B5CAF9A12A3A97639F21687AED38B7BAA4DE248EBE9C945411B6D9EDDC5631BFE5F31DDADF5B7E7D53BD49544ADFF8DE2431AEB7D7FAA8C8834F7DE5EF7E3BAED269E15D5595DB5A038A017A7BBF55C9F1AF41FAD3EA663710D94DFA7B290C8BBD1E924146EC5E0E7D1A0B6F1540BBB8BB97067AFF556FE07D85C4BEDF364440F863D53626ED63C7353F82090C1BE4FFBC5139B1AFEC57035C85A9E74F67DBCD57F2FAF2ACD12A05B2071485AC96A21E76231229F321EC56E34D58E66DD5770751A6247D6B0B0CCAACD85BFFB8619B9E1AA8379B4B2F2EAB62FD2A38F65717C58D7EEBDBB5CAD73D6FDF4B4D8FB59737250E62F7F36FBD56C3EED5BB3EE1E3AA6AA1ECE4BF3DB554D14F94DA0EA5715356A5D90546F8821815FBC6ED77554AE416061C71A6A69EA952E27B2328F7F5A3AA3B95ED8AE2B13B666E943F747AE96666BD98EF9DF1A6B7F32FB767D41B1FDA27D8538062CF487E6E29EB2E4326ABE747818D5484DA0EA7D6B855A5C4D4AFC45E90C7732B4E6AA113C5F24DD828DF9EC4FA8559295DA8E1B4337F8E758EC5FB84CC7AE06A5F6A7947F5F9F5CF56FCDA0EC7FAE435708B262C31625CCCEAED473DE674BACDD0852B6F96915B89D7A3BA9F30FBE76F61BFC99D95947FFC5B6B157AF4ADED50F48DD281C756986C8FA7B7BF0FDE2C236EBB635DB6B3D49C597C1EFE09DAACE4015827EE2E833D2A610D5F18A3629F9A8EB22C3742DE7063D8B96EF2BAF4E6A0900D7BA9B5BAE4F5CDCF56617C1AE59DCE11BDD873194CB2C7D3DB37AE3ACBEFCBD33123EB2E713567A69FB44B03D216C98C65ED7BDB8199F7F7B43A888962566FEF8D7B0FAFC276B67C68BB00CF522359187814F4FB1D66B773461C16C4D899D5DBA77FCFA852E2E63660A1CB5FCDBA346A0BDA1E3C7FD4B6DC425F63CBDE9DCC8F688300E6336C90FF64DA3D6C57FA34407FDF38FBD159A0EABB96166C2E35D52EC49E6FBB9F601E320F9761B19F5B5AC9A962E2F0BC1CB5C3B7BEB9E7EA969FCEC79FAC7A6B8AB7FFC55B534C2FB6EB1FE18CF01835CA3B5EE633BBA33A08804961DC925EFA55E7ECAADDE1BF0E3DBBAA68EBD2F6359D1FE6F6BBD4FCBA3AF353DFBB18707141714F0DD5F7BE466EB646CA3AD9D0D6F00CB9F90F0FCAB8D87775F8C9EAE78DF0E4775DD389CD17435ED3DA2D3DC1C7664BA7210FAB4A6DAE640668B6ECFA4769DAE2AA558AEEE3345ACB0D641E36F362EF1C7AD79E9C61273F7B50F0C98633702D64BB1F1133FCB113ADD1A9EF1F16F6BB7F6DE9D4D972EF73735E7AED7D6761B25DF99D4A6FFBD1BAAFAE557FF58311D0EF02741EB0C35E1D94A48047687A7795475BCAEA7EE054B8A0DF1BF1767DDBDD275E0D5ADB007A05C2BE1C48646EEC1DFD9E54D1D66FBE1A2348C1C9778EB565E7CF223C5D275AE57B9E6F3182D847C49336C4307190EF71EE51CD6F15B531BFAE7563EC68F6BD9D47CD6DEDBA87085ADA5BF1D187CAE195B7DB8BF6BE3D49C3D899DDDB23367A7B0423F68038660FF2018C00B107C421F68038C41E1087D803E2107B401C620F8843EC0171883D200EB107C421F68038C41E1087D803E2107B401C620F8843EC0171883D200EB107C421F68038C41E1087D803E2107B401C620F8843EC0171883D200EB107C421F68038C41E1087D803E2107B401C620F8843EC0171883D200EB107C421F68038C41E1087D803E2107B401C620F089348FC0FD5FF0F32C463FFDF0000000049454E44AE426082, NULL

The report design is now like this:

The legend column only displays if the Order has a maplegendimage, the map column always displays, but the image is taken from the database column mapimage.

Hope this is what you were after, but if not let me know and I'll explain what was wrong with the original report.

MM

select geometry::STGeomFromWKB(0x0106000000020000000103000000010000000B0000001000000000000840000000000000003DD8CCCCCCCCCC0840000000000000003DD8CCCCCCCCCC08408014AE47E17AFC3F040000000000104000CDCCCCCCCCEC3F9C999999999913408014AE47E17AFC3F9C99999999991340000000000000003D0000000000001440000000000000003D000000000000144000000000000000400400000000001040000000000000F03F100000000000084000000000000000401000000000000840000000000000003D0103000000010000000B000000000000000000143D000000000000003D009E99999999B93F000000000000003D009E99999999B93F8014AE47E17AFC3F400000000000F03F00CDCCCCCCCCEC3FA06666666666FE3F8014AE47E17AFC3FA06666666666FE3F000000000000003D1800000000000040000000000000003D18000000000000400000000000000040400000000000F03F000000000000F03F000000000000143D0000000000000040000000000000143D000000000000003D, 0);

PSB SSChampion Points: 13195 More actions · Answer 5

Thanks for the solution . I want Order2 to utilize (Legend1 + Order1) space and not shift to the left .

Example Legend takes = 3cm and Order1 takes 4 cm then Order 2 should be 3+4 = 7 cm. Is this possible ?

This is the reason I used two datasets instead of one .

Thanks,

PSB

mister.magoo SSC-Forever Points: 47174 More actions · Answer 6

i see.

i would add a third column whose width matches the width of columns 1 and 2 added together, and fill it with the image again, so you now have two columns with the image in them.

Change the visibility of column 2 to match column1 and column3 visibility to the opposite, this will then use columns 1 and 2 for Order1 and column 3 for Order2

not at my desk right now, but will upload a sample later if you need it.

MM

select geometry::STGeomFromWKB(0x0106000000020000000103000000010000000B0000001000000000000840000000000000003DD8CCCCCCCCCC0840000000000000003DD8CCCCCCCCCC08408014AE47E17AFC3F040000000000104000CDCCCCCCCCEC3F9C999999999913408014AE47E17AFC3F9C99999999991340000000000000003D0000000000001440000000000000003D000000000000144000000000000000400400000000001040000000000000F03F100000000000084000000000000000401000000000000840000000000000003D0103000000010000000B000000000000000000143D000000000000003D009E99999999B93F000000000000003D009E99999999B93F8014AE47E17AFC3F400000000000F03F00CDCCCCCCCCEC3FA06666666666FE3F8014AE47E17AFC3FA06666666666FE3F000000000000003D1800000000000040000000000000003D18000000000000400000000000000040400000000000F03F000000000000F03F000000000000143D0000000000000040000000000000143D000000000000003D, 0);

David Burrows SSC Guru Points: 65142 More actions · Answer 7

Use one tablix with two rows

row 1 two columns legend+map

row 2 one column (merge cells) map

and use row visibility

Far away is close at hand in the images of elsewhere.
Anon.

mister.magoo SSC-Forever Points: 47174 More actions · Answer 8

David Burrows (5/14/2015)
Use one tablix with two rows
row 1 two columns legend+map
row 2 one column (merge cells) map
and use row visibility

yes, that's even better.

MM

select geometry::STGeomFromWKB(0x0106000000020000000103000000010000000B0000001000000000000840000000000000003DD8CCCCCCCCCC0840000000000000003DD8CCCCCCCCCC08408014AE47E17AFC3F040000000000104000CDCCCCCCCCEC3F9C999999999913408014AE47E17AFC3F9C99999999991340000000000000003D0000000000001440000000000000003D000000000000144000000000000000400400000000001040000000000000F03F100000000000084000000000000000401000000000000840000000000000003D0103000000010000000B000000000000000000143D000000000000003D009E99999999B93F000000000000003D009E99999999B93F8014AE47E17AFC3F400000000000F03F00CDCCCCCCCCEC3FA06666666666FE3F8014AE47E17AFC3FA06666666666FE3F000000000000003D1800000000000040000000000000003D18000000000000400000000000000040400000000000F03F000000000000F03F000000000000143D0000000000000040000000000000143D000000000000003D, 0);

PSB SSChampion Points: 13195 More actions · Answer 9

Please attach the sample report and thanks so much for helping!

mister.magoo SSC-Forever Points: 47174 More actions · Answer 10

There you go - this time with RowVisibility, which is a better way for your needs.

MM

select geometry::STGeomFromWKB(0x0106000000020000000103000000010000000B0000001000000000000840000000000000003DD8CCCCCCCCCC0840000000000000003DD8CCCCCCCCCC08408014AE47E17AFC3F040000000000104000CDCCCCCCCCEC3F9C999999999913408014AE47E17AFC3F9C99999999991340000000000000003D0000000000001440000000000000003D000000000000144000000000000000400400000000001040000000000000F03F100000000000084000000000000000401000000000000840000000000000003D0103000000010000000B000000000000000000143D000000000000003D009E99999999B93F000000000000003D009E99999999B93F8014AE47E17AFC3F400000000000F03F00CDCCCCCCCCEC3FA06666666666FE3F8014AE47E17AFC3FA06666666666FE3F000000000000003D1800000000000040000000000000003D18000000000000400000000000000040400000000000F03F000000000000F03F000000000000143D0000000000000040000000000000143D000000000000003D, 0);

PSB SSChampion Points: 13195 More actions · Answer 11

PSB

SSChampion

Points: 13195

May 14, 2015 at 11:47 am

#1797945

Great ! Thanks a bunch . 🙂