"An  occurred during setup of Reporting Services extensions. Reason: Unable to find appropriate service endpoint information in the configuration object"

Problem: The above pattern is bad in different ways

       1. Base classes must have references to the sub classes and that makes it tightly coupled.

       2. Following the Open-Closed principle  (open for extension and closed for modification), we do not want to open the code for changes when in future a new class is introduced that derive from the base class.

I am using the https://en.wikipedia.org/wiki/Factory_pattern

The factory method pattern is an object-oriented creational design pattern to implement the concept of factories and deals with the problem of creating objects (products) without specifying the exact class of object that will be created. The essence of this pattern is to "Define an interface for creating an object, but let the classes that implement the interface decide which class to instantiate. The Factory method lets a class defer instantiation to subclasses."^[1] 

Solutions: to make our pattern loosly coupled and Open-Closed, I prototyped a quick example in .Net using reflection. 

we want some like this.

Prototype: I created the following classes

    1. ExtensionClassFactory.cs ----> Implements the Factory

   2. ConnectionAttribute.cs     ------> Processes the Attributes that decorate the classes.

   3. Interface with 2 derived classes  (IConnection.cs is the interface, Connection1.cs, Connection2.cs are the derived classes)

Here if you see we are just passing an input to the IConnection interface. Based on the input the corresponding derived class is instantiated.

                  RESULT ----  "Hi! I am in Connection1" is read from Connection1.cs

How is it done: Implement the following classes.

1. INTERFACE CLASS - that defined the method implemented by derived classes

2. Sample Connection1.cs class that implements derived class1

3. Sample Connection2.cs classs that implements the derived class 2.

 4. EXTENSIONFACOTRY - is implemented using REFLECTION to read the attribute that decorates the CLASSES (DERIVED CLASSES

  The factory will be given the base class and the attribute value, it will looking for the derived classes and or this attribute type value combination.

1. Using AOT. (right click AOT>Forms nodes and add a new form. You add controls under 'Design' sub node and tables under 'Data Source' subnode)

OR

2. Using X++ code to dynamically create and display a form.

X++ Dynamic Forms: 

1. FORM and FORMRUN classes can be used to create forms using code.

2.  AOT > System Documentation > Classes >  Form** classes - Look here for the list of all the Form Classes.

              Form Classes categories:

[1] FormBuild Classes are used to design a form in the code.

ex: FormBuildDataSource, FormBuildDesign, FormBuildGridControl, FormBuildButtonControl, FormBuildStringControl

[2] FormRun Classes are used to control the form elements during the run time.

ex: FormDataSource, FormDesign, FormTabControl, FormGridControl, FormButtonControl, FormStringControl etc.

FormBUILD classes to design a form

      1. Create a class with Main method. see the example below

-Create Form Header,

-Add Data Source,

-Add elements to Design node. (Add TabControl > Add TabPageControls > Add Grid Button & String Control to the TabPage controls)

  Output before click:

FormRUN class: to modify the forms on the fly.

                     1. In above example this piece of code will override the Form button control clicked method with a method (method1) defined in our example  class (AAClass1).

                   2. Create a new method in Class 'AAClass1\method1'. - when button is clicked 'registerOverrideMethod' will redirect the call to method1.

- Get the handle of the button and find the parent of parent of the button (i.e. TabPage and then Tab control),

- Add new TabPage control, Add String Control to the new TabPage

Output after click - when the button 'a' in the above example is clicked. A new Tab Page is created and new String control is added to this TabPage control displaying the first column of the data source.

- are like virtual tables that use fields and rows to represent the data record.

- data in a View is not stored as data base object but is dynamically created when view is accessed.

Where? all the places where tables are used.

                         Forms ; Queries ; Reports ; x++ code 

Why Views?      - Focussed Data (only relevant data by picking the relevant fields)

- Customized Data (a single table view from multiple data sources can be created)

- Performance (becaused view definition is created compiled; and is better than complex query)

Create a View:

AOT > Data Dictionary > Views <right click - new View>

Metadata -  query or data source to get the data. Also called View Query

      ** only single table / view / query / map is added to metadata

- right click Data Source > New Data Source : select the [properties] tables from the list

- or drag and drop the data source (table/view/query/maps)

- or in the property on View node [ Query=queryName ] to add a query

Fields -  has data fields of view Small subset of fields

[properties]: Dynamic=Yes [all fields in data source are visible]

                                  = No [can pick selected fields]

Field Groups - logically group the fields.

Methods - add new or override method on xRecord class

Note: unlike SQL view, AX views are read only.

Note2: View created above will generate view definition and store in database. In the SQL management studio you can the view created in AX View.

 Views vs Queries?

             View can be created for single data source (table/view/query/map), but if you want to work with multiple data source then use Query.

             to take performance advantage of view you can add Query to the metadata so that data can be retreived from multiple data sources             

How to view: Browse like how you browse a table. Right click ViewName >Add-Ins >Table browser

How? you need the following classes Query; QueryRun; QueryBuildDataSource; QueryBuildRange; QueryBuildLink

CodeSample1: x++ code to dynamically create a query. verify the results in the Infolog.

CodeSample2: will show how to create a node on AOT. In the query example I am showing how to generate dynamic query object and use it to construct a node on  AOT\Query node.

(also showing how to use macros like #AOT, #QueriesPath)

How to get data in AX: 1. Views, 2.Queries  3.Select statement.

Why Queries?

  helps when ranges or values are not known until run time.

Where used?

  in forms + reports + places where data is retreived from multiple data sources.

How to create?

         1. AOT > Queries : (aka static queries) this node has predefined static queries, and you can add queries (Right Click on AOT\Queries node >Add Query)

Methods: customize or override methods of QueryRun class

DataSources: can be table, map, view --- and each of them can be nested as parent and child

Fields: check the Dynamics[property] : Yes mean all fields are displayed; No means you can pick fields

Range: to limit records for a given Range expression. ex: "1000" "1000..3000" "<2000" ">=4000" etc

GroupBy: only specific field combinations.

OrderBy: sort order to sort results. ex: ascending descending.

DataSources: can nest multiple data sources and link them using relations. (see pic below)

Relations: to set the join mode between the tables like Inner, Outer etc.

Dependent Object: All AOT nodes that refer the query are displayed here. ex: Forms, reports and other affected objects.

Composite Query: query based on another query. It is like inheritance. Usually used to override or add further ranges.

         2. x++ dynamic Queries:

check the next blog post.

Reason:

Because of conflict with the .Net versions the error is thrown.

Solution:

Clear the vairable complus_version or set the complus_Version to latest .NET version. In my case I changed from v.2.0.xxxx. to v4.0.30319. you can verify the latest .Net version from the folder  C:\Windows\Microsoft.NET\Framework

Issue: Often when you try to register a DLL on Win7 or windows server 2008, you run into an error

     "The module scmt.dll was loaded but the call to DllRegisterServer failed with the error code 0x80040201"

Why:  UAC (user account control) limits the ability to register the DLL. so you have to run the command on elevated command prompt using Admin role.

Fix: Run the command in an elevated mode

   1. Click on Start button > type Command Prompt > (right click command prompt and click run as Administrator)

   2. Deregister the DLL using the following command 

                         cmd> "regsvr32 /u scmt.dll"

   3. Reregister the DLL using the command

                         cmd > "regsvr32 scmt.dll"

   you will get the below dialog box.

Usually Database snapshots provide static view of the source database, and are mostly read only view of the database.  

However sometime when you try to restore the database with snapshots we may get the following error SQL message:

Error:
"Msg 5094, Level 16, State 2, Line 2

The operation cannot be performed on a database with database snapshots or active DBCC replicas.

Msg 3013, Level 16, State 1, Line 2

RESTORE DATABASE is terminating abnormally."

Quick FIX: (solution)

  1. Create a new DataBase and then restore the snapshot against it.

  2. Try renaming the database before restoring,

  You need to install Terminal Services for multiple session to work. Complete the Wizard all the way till finish and it will prompt you to restart.

2. Click on Start > Run

       Type  "gpedit.msc" and click Enter

3. Launch Local Policy Editor and browse to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connection

          Edit the Policy Setting for "Allow users to connect remotely using Remote Desktop Service" and also Edit the "Limit the number of connections"