Topics covered this month include:

 

SQL Server Compatibility 

Helpful Hints for SSRS Formulas 

Resizing PVs 

The new SL Partner Forum 

More about the New Hotfix Download Process 

 

 

 

SQL Server Compatibility

You can now use SQL Server compatibility mode 90 with your Microsoft Dynamics SL databases. Compatibility mode 80 is still supported and remains the default mode for new or upgraded databases created by Database Maintenance (98.290.00). However, Dynamics SL 7.0 FP1 is the last release in which compatibility mode 80 is the default. SQL Server compatibility mode 100 is not currently supported.

 

You may want to change to compatibility mode 90 now. If you have custom SQL or third- party applications, follow the steps listed in the SL 7.0 FP1 Notes to Implementers document under “Preparing Databases for Compatibility Mode 90.” Otherwise, go directly to “Setting the Compatibility Mode to 90.” instructions in the Notes to Implementers document.

 

Important: Perform the preparation steps in a test database first before using them with your production databases. After tests of the changes are successful, follow the steps in “Setting the Compatibility Mode to 90” to apply the changes to your production databases.

Helpful Hints for SSRS Formulas - contributed by Don Shields, ClientsFirst-US

Need help with creating SSRS formulas?  Don has compiled a list of formulas and reference sites that he has used over the years and has generously agreed to share this information with us.  See his notes below.

Web pages to reference:

http://www.w3schools.com/vbScript/func_formatnumber.asp

http://www.w3schools.com/Vbscript/func_formatcurrency.asp

http://www.w3schools.com/Vbscript/func_formatpercent.asp

 

List of formulas to use for different functions:

Append two fields together in one cell:

=Fields!AccountNum.Value & ": " & Fields!Name.Value

Formatting a formula as a number with 2 decimals:

=Formatnumber(sum(fields!lineamount.value),2)

Page Numbers:

="Page: " & Globals!PageNumber & " of " & Globals!TotalPages

Execution date/time:

=formatdatetime(Globals!ExecutionTime,1)

= countdistinct(Fields!SalesId.Value)

=Formatnumber(formula,2)** see more options.

=formatpercent(formula,2,-1,-1,-2)**

=iif(Fields!ValidFrom.Value<"1990-01-01"," ",formatdatetime(Fields!ValidFrom.Value,2))

Visibility hidden formula using “Show Details”

=iif(Parameters!ShowDetails.Value="True", False,True)

Toggle behavior on toggle field (initial toggle state):

=Parameters!ShowDetails.Value

Row Numbers:

=RowNumber("table1_Group2")

Conditional format using an iif() statement:

=iif(RowNumber("table1_Group2")=1,"$ " & formatnumber(Fields!LineAmount.Value,2,-2,-1),formatnumber(Fields!LineAmount.Value,2,-2,-1))

Conditional Value using the switch() statement:

switch(Fields!QuotationStatus2.Value = 2,GetProjTotal(Fields!QuotationId.Value),

Fields!QuotationStatus2.Value <> 2,0, condition3, value3, ...)

Note that the Switch statement is similar to a CASE() statement in SQL.  It's a lot better than using nested iif() statements in certain circumstances.

 

Resizing PVs 

Ever have difficulty resizing an existing possible values window - and keeping the changes intact?  We found this tip on the (old) Solomon Partner Forum:

If you manually enter the pvleft, pvwidth, pvheight, and pvtop properties in the customized field in a CST file, and then reimport the CST file, the PV for that field can be resized and the settings will be saved when the screen is closed.

 

Have you accessed the new Microsoft Dynamics SL Partner Private Newsgroup that replaced the Solomon Partner Forum on August 1, 2009? 

There was some confusion about the initial link to use to get started - the correct link can be found here.

 

More about new hotfix downloads...

Why are hotfixes now being published to the Knowledge Base instead of on CustomerSource and PartnerSource under Support->Hotfixes? 

Publishing hot fixes to the Knowledge Base provides longer descriptions/symptoms and when available, details causes of the problem, workarounds and "fixed in GA" version information within the KB article.  Only a short description was provided in the CustomerSource/ PartnerSource postings.

Why is it now a two step process to download a hotfix? 

After clicking on the link at the top of the article, you are prompted to select the hotfix, then provide your email address and submit request.  An email is then sent with a link to the actual download. Why is this approach being used?  This process allows Microsoft to have a list of who downloaded a particular hot fix.  In the event a problem is found with the file and it needs to be pulled, there is now a mechanism to notify those who downloaded it.

How can I streamline my searches to pull up only hotfixes for the version I use? 

Enter the full product name and version in quotes, followed by the word hotfix:

"Microsoft Dynamics SL 7.0 Feature Pack 1" hotfix

By putting the complete product name and version in the quotes, it forces the search to only return articles that contain that exact sequence of words.  You are basically saying, give me all results that contain "Microsoft Dynamics SL 7.0 Feature Pack 1" AND "hotfix".

To expand on this further, if you had everything in quotes: "Dynamics SL 7.0 Feature Pack 1 Hotfix", you would get all results that contain "Dynamics" and "SL" and "7.0" and "Feature" and "Pack" and "1" and "Hotfix", regardless of the order in which the words exist in the article and regardless of whether 6.x is also discussed in the article. 

Is there a document to walk me through the new steps needed to find and download a hotfix? 

Yes, here is a step-by-step guide: 

1.      Click “View and Request hotfix downloads” at the top of the KB article.

2.      The following window opens.  Click to select which version of the hot fix you want to download, type the characters displayed in the picture shown for security purposes, and then click Request hotfix.


3.      Receive the following confirmation:


4.      Receive an e-mail that resembles the following.  Scroll down and see the download link and password.


 

5.      Click the link, and then save the self-extracting file.

 

6.      Extract the file and specify the password from the e-mail during the extraction process.