Hi--any report writers out there?
I'm new to SSRS and don't make report edits very often even in Infomaker.
I am trying to make what I think is a simple change, just changing the justification of two data outputs to be right justified to match the rest of the report column.
I assumed changing this "TextAlign" property would do the trick, but it's not. Oddly all of the items from the screenshot above had "default" as their "textalign" property, so maybe that is not what will fix it?
I wonder if there is a lag or trick to get it to update to Tessitura? I recall there is something like that with Infomaker.
Any tips for webinars or other training for improving my knowledge in this area would be helpful. I searched the site but only found stuff that was 10+ years old.
Thanks for your help!
Kanani
To make sure you're updating properties for the right element, be sure you have the text box highlighted - rather than the expression inside the box. You should see the update in Tessitura as soon as you deploy the .rdl.
When you say "deploy" do you mean you have to do something more than save it?
Separate from saving, from Build menu, choose Deploy to push your changes to the SSRS server.
Follow Chris' direction on the deploy. if that doesn't work you can open a ticket to have them look at your deploy settings. (You can deploy to live or test, depending on the settings.)
Are you supposed to deploy solution or deploy custom Tessitura? I chose the later and got a lot of error messages, HOWEVER one of my boxes is now right justified. I don’t understand why the other one didn’t change. Alignment settings on both are right.
You can deploy just the .rdl that you're working on. Another way to do it is by finding the rdl in the solution explorer pane (usually on the right side of the screen) and right-clicking on it and selecting "Deploy". You may see it build all of the rdls in the solution - that is ok, and nothing to worry about if it gives you warnings about those other rdls.
Deploy Custom is correct. There are several setting in the Configuration Manager that you may need to review. Depending on what they are set on, they can cause errors or a smooth deployment.
If you are deploying to PROD, you want to ensure the Configuration Manager is set to Release and that the path to the PROD report location is set in Configuration Manager to the correct path where the files are located.
To deploy to TEST, you would set Configuration Manger to Debug. Your path for that would have to be pointed to the TEST path where the report files are stored.
You can find the Configuration Manager settings by right-clicking on the Tessitura_Custom solution in the Solution Explorer and choosing Properties. Be careful with changing these settings as, as you found, if they aren't set properly you will receive errors when you deploy.
Brian Graham I tried deploying it again. I'm on RAMP and working in TEST. The location looks correct to me (see bottom of screen shot). So I assume there's something wrong with how I'm selecting the box, as the purchase order box is now right justified and the Grade/school type box still isn't. Can you look at this and tell me if you see anything that looks wrong about how I'm selecting the box?
Weird... I'm not seeing anything wrong with that. Seems like that box should now be right-justified. Any chance you have the wrong rdl? Are other changes reflected in test after deploying?
Yep, glad I'm not the only one who thinks this is really weird. I just added "TEST" to the report name as a test, and the change updated after saving and deploying. Here it is run in Test Tessitura.
Wondering if the answer is in the data... If you run the proc in SSMS and copy the value out of that field and paste it somewhere... any chance there are a bunch of trailing spaces on the right side of value?
Ding ding ding! You win.
Well, I couldn't easily figure out where the extra spaces were coming from, so I decided to left justify everything and that solves the problem. Thanks everyone! I learned a lot and solved my issue. Thanks!
If you are comfortable with editing the code, using the RTRIM or LTRIM functions in SQL will remove the spaces, if they exist.
Good catch on the spaces Brian Graham!