API/CodeSamples/ExtendedFunctions.md
... ...
@@ -4,10 +4,18 @@
4 4
5 5
##About
6 6
7
-This list allows the user specify additional SQL functions that should be included in the functions dropdown of the Fields tab.
7
+This list allows the user specify additional SQL functions that should be included in the functions dropdown of the Fields tab. You can also enable functions in an [[Expression|http://wiki.izenda.us/API/CodeSamples/ExpressionFunctions]]
8 8
9 9
Below is a sample global.asax using the ExtendedFunctions setting. The code block will appear within ``<script runat="server"> </script>`` tags within global.asax.
10 10
11
+##Best Practices
12
+
13
+* If a function will be used ONLY in an Expression, then you should use the ExpressionFunctions setting. Otherwise, use ExtendedFunctions to allow the function to be placed into the dropdown Function list in the report designer.
14
+
15
+* You should not use parentheses when you specify a function in ExtendedFunctions or ExpressionFunctions. All we want to do in these settings is list the function name itself, and not call the function.
16
+
17
+* When you specify a function in ExtendedFunctions you should use the full function name with schema. When you specify it in ExpressionFunctions short name is sufficient.
18
+
11 19
##Global.asax (C♯)
12 20
13 21
```csharp