SSRS - How to Parameterizing the SQL Query

1. We need to create separated dataset to handle the pre defined list in that dataset we will use simple select statement to define the list : 

SELECT    Number  FROM         Table 1 WHERE    ORDER BY Number

1. In the main dataset when we create the Query in the we will filter the column with parameter e.g.  we put in the Filter column for Number  “= @SerialNumber”  this allows the user to specify a serial number at the time the report is run
2. please click on below  link  to access the original artical

http://www.dynamicssol.com/ShowArticle.aspx?ID=60 

Delegation

Delegation is type which can be used to save reference to method (procedure /function). Since delegation is a type so we should think it is something like data types then we can define variable of that delegate (type) and then we can use this variable as reference to method.

The declaration of the delegation same of the declaration of the method with one exception delegation will not have body (no code), and the declaration represent signature of method so it will contain return value and parameters.

Delegate  <return Type> <MethodName> (type  Prameter1,type  Pramter2)

Delegate double processMath(double  param1 , double param2)

 

1. First declare delegate processMath which have signature same of method1 & method2
2. Declare variable process of the delegate (this variable will have type as delegate)
3. Initiate the variable process by using the contractor, process= new processMath (Divide)  , as we see when we Initiate the variable we pass the method name as parameter which not match with the declaration of the delegation, but that method has signature same as of the delegation .
4. Finally we will call the variable which represent the method and we will pass the parameters.

Object Oriented Programming - OOP

Class & Object:

• Class it is like an data type and Object like variables.
• As we can define variable MyString and Type will String
• Also we can define Object MyObject and class will be Class A
• Any Object will represent an instance of Class
• We can define more than one objects belong to same class, as we can define more than one variables with string type.

 

 

Properties & Fields

• Properties and fields will give accessibility to the Object  Data
• Object data which the things that differ each object from other objects which belong to same class. For example if we want to represent the coffee in OOP we can assume we have Class call it  CupOfCoffee we can have different objects belong to that class , if we assume the CupOfCoffee class will have filed call it coffee name so we can have the following objects:
  • Object1:Turksh Coffee
  • Ojbect2: Nescafe Coffee 

• As we can see we can differentiae the two objects based on the value of Name Field

To access the full version of this article please refer to the following link

http://www.dynamicssol.com/ShowArticle.aspx?ID=51

  :

How to create more than one organization in CRM 4- Part1

There are two common method to create more than one organization in CRM 4 configuration , in both ways we have to use Deployment Manager utility which will help us to create the new organization. To open the Organization Deployment Wizard  we need to use the Deployment Manager utility.


 

To access the full version of this article please refer to the following link

http://www.dynamicssol.com/ShowArticle.aspx?ID=57

Firefox Error in parsing value for 'height'. Declaration dropped

I have developed Java Script to find the height of columns height and make it match for all columns in the web page but I was getting an  error “Error in parsing value for 'height'.  Declaration dropped” in the Firefox but in IE it is working fine without issue, then we I cross checked the script I found the issue I forget to define the unit of measure, so I just added the unit of measure and this issue resolved, following the old code and new code.

Old Code

   function msetcontainer() {

        if (document.getElementById) {

            var windowHeight = getWindowHeight();

            if (windowHeight > 0) {

                var contentHeight =

        document.getElementById('rightcol').offsetHeight;

                var contentID = document.getElementById('rightcol');

                var LeftcontentHeight =

        document.getElementById('leftcol').offsetHeight;

                var LeftcontentID = document.getElementById('leftcol');

                if (LeftcontentHeight != contentHeight) {

                    contentID.style.height = LeftcontentHeight;

                }

            }

        }

    }

New Code

   function msetcontainer() {

        if (document.getElementById) {

            var windowHeight = getWindowHeight();

            if (windowHeight > 0) {

                var contentHeight =

        document.getElementById('rightcol').offsetHeight;

                var contentID = document.getElementById('rightcol');

                var LeftcontentHeight =

        document.getElementById('leftcol').offsetHeight;

                var LeftcontentID = document.getElementById('leftcol');

                if (LeftcontentHeight != contentHeight) {

             //there was issue with firefox becasue i forget to add + 'px'

                    contentID.style.height = LeftcontentHeight + 'px' ;

                }

            }

        }

    }

eConnect error 475 - taRMTransaction

Terms Discount Taken Amount (DISTKNAM is not valid for Credit Memos and Returns (RMDTYPAL = 7 or RMDTYPAL =8).

Sometimes you will get this error when you are calling the eConnect method taRMTransaction to create returns (RMDTYPAL =8) or credit memos (RMDTYPAL =7)receivable transaction but you’re passing terms discount taken amount (DISTKNAM) in the  method taRMTransaction, the reason both credit memos and returns are credit documents and in the MS Dynamics GP terms discount not applicable for the credit documents, as solution if when you are creating returns / credit memos transaction don't pass value in PYMTRMID.

eConnect error 474 - taRMTransaction

Payment Terms (PYMTRMID) are not allowed on Returns (RMDTYPAL = 8) .

Sometimes you will get this error when you are calling the eConnect method taRMTransaction to create returns receivable transaction but you’re passing payment terms , actually the returns are credit document and the payment terms applicable only for the debit document. in receivable transaction entry window of MS Dynamics GP when user select document type as Returns system by default will disable the payment terms field, lockup and expansion button to stop the user from adding the payment terms, same validation has been build in the eConnect and because of that system throwing this error "Payment Terms (PYMTRMID) are not allowed on Returns (RMDTYPAL = 8) " so as solution if when you are creating returns transaction don't pass value in PYMTRMID.

eConnect error 9522 - taRMTransaction

Batch Checkbook ID (BatchCHEKBKID) is set to inactive in the Checkbook Master Table - CM00100.

Sometimes you will get this error when you are calling the eConnect method taRMTransaction and you’re passing checkbook ID which was inactivated in the checkbook master (CM00100). To get rid from this issue you need to be sure checkbook ID which you passing to the eConnect method is active you can run the following query before you call the taRMTransaction method:

if (exists SELECT 1 FROM CM00100 (nolock) WHERE CHEKBKID = 'xxx' and INACTIVE = 1)

begin

record an error in the error log and dont call the econnect taRMTransaction method

end

Note: replace the xxx with your check book.

eConnect error 363 - taRMTransaction

Batch Checkbook ID (BatchCHEKBKID) does not exist in the Checkbook Master Table - CM00100.

Sometimes you will get this error when you are calling the eConnect method taRMTransaction and you’re pass checkbook ID which not been defined in the checkbook master (CM00100). To get rid of this issue you need to be sure checkbook ID which you passing to the eConnect method already exists in the Checkbook Master you can run the following query before you call the taRMTransaction method:

if (not exists SELECT 1 FROM CM00100 (nolock) WHERE CHEKBKID = 'xxx')

begin

record an error in the error log and dont call the econnect taRMTransaction method

end

Note: replace the xxx with your check book.

One more option if you used above query and the provided checkbook ID not defined in the system you other than quit the process you can call eConnect method taCreateCheckbook method to create the checkbook master and then you can processed with calling the taRMTransaction method.

If there is no business need to assign specific checkbook to the AR batch you can ignore the BatchCHEKBKID element of the taRMTransaction method and in the background eConnect will access the Receivable setup and get the default checkbook ID which has been defined and system will use this checkbook ID while creating the AR batch.

eConnect error 241 - taRMTransaction

Document Number for the Cash Payment (DCNUMCSH) already exists in the RM Keys Master Table - RM00401.

sometimes you will get this error when you are calling the eConnect method taRMTransaction and you’re trying to create a AR document (Invoice , Debit Memo) and on same time you are trying to collect the cash on fly as per eConnect functionality user can collect the cash directly in the AR document (Invoice , Debit Memo) by providing the following details:

Cash Amount                        

Checkbook ID Cash                                                

Cash Date

Document Number Cash        

This issue could occur because Document Number Cash / RMDTYPAL=9 (Cash) which system pass to  eConnect has document already exists RM Keys Master Table, there could be many reasons behind this issue e.g. if you are calling eConnect or any other script to generate the cash document number and if this script failed to update the next document number properly you will end with this issue.

As solution before you call the taRMTransaction. you need to verify the cash document number which you passing to eConnect and if the document number already exists in RM00401 then you can get another document number, also you can through an error in the integration process and you can investigate more behind this issue.

eConnect error 206 - taRMTransaction

Check Amount (CHEKAMNT) > 0 but the Checkbook ID for the Check (CBKIDCHK) is missing.

This issue could occur if you’re trying to create a AR document (Invoice , Debit Memo) and on same time you are trying to collect the cash on fly (cash type =Check) and you did not pass Checkbook ID , as per eConnect functionality user can collect the cash directly in the AR document (Invoice , Debit Memo) by providing the following details:

• Check Amount        
• Check Number                
• Checkbook ID Check                                                 
• Check Date
• Document Number Check         

Note: the all the above parameters are optional in the definition of the taRMTransaction method but if you provide value in the check amount field all those fields will become as required parameters and user has to provide the proper values.

eConnect error 205 - taRMTransaction

Cash Amount (CASHAMNT) > 0 but the Document Number for the Cash Payment (DCNUMCSH) is missing.                                                                                                                                                                 

This issue could occur if you’re trying to create a AR document (Invoice , Debit Memo) and on same time you are trying to collect the cash on fly (cash type =Cash) and you did not pass Document Number for the cash receipt, as per eConnect functionality user can collect the cash directly in the AR document (Invoice , Debit Memo) by providing the following details:

• Cash Amount        
• Cash Number                
• Checkbook ID Cash                                                 
• Cash Date
• Document Number Cash         

Note: the all the above parameters are optional in the definition of the taRMTransaction method but if you provide value in the cash amount field all those fields will become as required parameters and user has to provide the proper values.

eConnect error 204 - taRMTransaction

Cash Amount (CASHAMNT) > 0 but the Cash Date (CASHDATE) is missing.

This issue could occur if you’re trying to create a AR document (Invoice , Debit Memo) and on same time you are trying to collect the cash on fly (cash type =Cash) and you did not pass Document Date, as per eConnect functionality user can collect the cash directly in the AR document (Invoice , Debit Memo) by providing the following details:

• Cash Amount        
• Cash Number                
• Checkbook ID Cash                                                 
• Cash Date
• Document Number Cash         

Note: the all the above parameters are optional in the definition of the taRMTransaction method but if you provide value in the cash amount field all those fields will become as required parameters and user has to provide the proper values

eConnect error 203 - taRMTransaction

Cash Amount (CASHAMNT) > 0 but the Checkbook ID for the Cash Payment (CBKIDCSH) is missing.
This issue could occur if you’re trying to create a AR document (Invoice , Debit Memo) and on same time you are trying to collect the cash on fly (cash type =Cash) and you did not pass Checkbook ID , as per eConnect functionality user can collect the cash directly in the AR document (Invoice , Debit Memo) by providing the following details:
1. Cash Amount        
2. Cash Number                
3. Checkbook ID Cash                                                 
4. Cash Date
5. Document Number Cash         
Note: the all the above parameters are optional in the definition of the taRMTransaction method but if you provide value in the cash amount field all those fields will become as required parameters and user has to provide the proper values

eConnect error 190 - taRMTransaction

Document number (DOCNUMBR) already exists in either RM00401, RM10301, RM20101 or RM30101.

This issue could occur if you’re trying to create a AR document (Invoice , Debit Memo, Credit Memo ..etc) which has document number / document type already exists RM Keys Master Table (RM00401) or RM Work table (RM10301) or RM Open(RM20101) or in RM History (RM30101), there could be many reasons behind this issue e.g. if you are calling eConnect or any other script to generate the document number and if this script failed to update the next document number properly you will end with this issue.

As solution before you call the taRMTransaction. you need to verify the document number which you passing to eConnect and if the document number already exists in RM00401, RM10301, RM20101 or RM30101 then you can get another document number, also you can through an error in the integration process and you can investigate more behind this issue.

eConnect error 648 - taRMTransaction

SQL error occurred inserting into the RM Keys Master Table - RM00401, sometimes you will get this error when you are calling the eConnect method taRMTransaction.
This issue could occur if you’re trying to create a AR document (Invoice , Debit Memo) and on same time you are trying to collect the cash on fly (cash type =Credit Card) as per eConnect functionality user can collect the cash directly in the AR document (Invoice , Debit Memo) by providing the following details:
1. Check Amount        
2. Check Number                
3. Checkbook ID Check                                                 
4. Check Date
5. Document Number Check         
This issue could occur because Document Number Credit Card/ RMDTYPAL=9 (Cash) which system pass to  eConnect has document already exists RM Keys Master Table, there could be many reasons behind this issue e.g. if you are calling eConnect or any other script to generate the Credit Card document number and if this script failed to update the next document number properly you will end with this issue.
As solution before you call the taRMTransaction. you need to verify the Credit Card document number which you passing to eConnect and if the document number already exists in RM00401 then you can get another document number, also you can through an error in the integration process and you can investigate more behind this issue.

eConnect error 647 - taRMTransaction

SQL error occurred inserting into the RM Keys Master Table - RM00401, sometimes you will get this error when you are calling the eConnect method taRMTransaction.
This issue could occur if you’re trying to create a AR document (Invoice , Debit Memo) and on same time you are trying to collect the cash on fly (cash type =Check) as per eConnect functionality user can collect the cash directly in the AR document (Invoice , Debit Memo) by providing the following details:
1. Check Amount        
2. Check Number                
3. Checkbook ID Check                                                 
4. Check Date
5. Document Number Check         
This issue could occur because Document Number Check / RMDTYPAL=9 (Cash) which system pass to  eConnect has document already exists RM Keys Master Table, there could be many reasons behind this issue e.g. if you are calling eConnect or any other script to generate the Check document number and if this script failed to update the next document number properly you will end with this issue.
As solution before you call the taRMTransaction. you need to verify the Check document number which you passing to eConnect and if the document number already exists in RM00401 then you can get another document number, also you can through an error in the integration process and you can investigate more behind this issue.

eConnect error 641 - taRMTransaction

SQL error occurred inserting into the RM Keys Master Table - RM00401, sometimes you will get this error when you are calling the eConnect method taRMTransaction.

This issue could occur if you’re trying to create a AR document (Invoice , Debit Memo) and on same time you are trying to collect the cash on fly as per eConnect functionality user can collect the cash directly in the AR document (Invoice , Debit Memo) by providing the following details:

• Cash Amount                        
• Checkbook ID Cash                                                
• Cash Date
• Document Number Cash        

This issue could occur because Document Number Cash / RMDTYPAL=9 (Cash) which system pass to  eConnect has document already exists RM Keys Master Table, there could be many reasons behind this issue e.g. if you are calling eConnect or any other script to generate the cash document number and if this script failed to update the next document number properly you will end with this issue.

As solution before you call the taRMTransaction. you need to verify the cash document number which you passing to eConnect and if the document number already exists in RM00401 then you can get another document number, also you can through an error in the integration process and you can investigate more behind this issue

eConnect error 609 - taRMTransaction

SQL error occurred inserting into the RM Keys Master Table - RM00401, sometimes you will get this error when you are calling the eConnect method taRMTransaction.

This issue could occur if you’re trying to create a AR document (Invoice , Debit Memo, Credit Memo ..etc) which has document number / document type already exists RM Keys Master Table, there could be many reasons behind this issue e.g. if you are calling eConnect or any other script to generate the document number and if this script failed to update the next document number properly you will end with this issue.

As solution before you call the taRMTransaction. you need to verify the document number which you passing to eConnect and if the document number already exists in RM00401 then you can get another document number, also you can through an error in the integration process and you can investigate more behind this issue and .

eConnect error 202 - taRMTransaction

Batch is currently being posted, sometimes you will get this error when you are calling the eConnect method taRMTransaction.

This issue could occur if you’re trying to create a AR document (Invoice , Debit Memo, Credit Memo ..etc) and you have assigned this  AR document to a receivable batch is currently being posted. To a void such kind of errors you need to be sure the batch number not been selected to be posted.

To check the posting status you can use call the following query before calling the taRMTransaction method. If the @BATCHSTATUS=1 this mean the specified batch is currently being posted so you should use another batch number.

if (exists(select 1 from SY00500 (nolock) where BACHNUMB = @BACHNUMB and MKDTOPST <> 0 and BCHSOURC = @BCHSOURC))

begin

/* The Batch (BACHNUMB) is currently being posted */

SET @BATCHSTATUS = 1

end



eConnect error 24

Customer Number (CUSTNMBR) does not exist in the Customer Master Table - RM00101, sometimes you will get this error when you are calling the eConnect method taRMCashReceiptInsert.

This issue could occur if you’re trying to create a cash receipt document for customer number which is not exist in the customer master (RM00101) as solution for this issue you can add script in the integration process to create the  customer master on fly if the master record not exist or we can create the  customer master manually before we run the integration.

eConnect error 18

SQL error occurred inserting into the RM Keys Master Table - RM00401, sometimes you will get this error when you are calling the eConnect method taRMCashReceiptInsert.

This issue could occur if you’re trying to create a cash receipt document which has document number / document type already exists RM Keys Master Table, there could be many reasons behind this issue e.g. if you are calling eConnect or any other script to generate the document number and if this script failed to update the next document number properly you will end with this issue.

As solution before you call the taRMCashReceiptInsert.you need to verify the document number which you passing to eConnect and if the document number already exists in RM00401 then you can through an error in the integration process and you can investigate more behind this issue.

eConnect error 13

Unable to update batch information in SY00500,sometimes you will get this error when you are calling the eConnect method taRMCashReceiptInsert.

This eConnect issue and it  occurred when system trying to create the batch number in the batch master table (SY00500) there are many reasons behind this issue e.g. wrong length for the batch number the batch number should not exceed 15 character or wrong format for the post date or wrong decimal places for the document amount. Or also it could happen due to the deadlock.