
From front end, we wrote logic to see if User has chosen 'All Clients' from dropdown, then do no send any value to CleintID parameter which mean default value null. So, instead of sending parameter value as 'All' for ClientID, we declaredĭefault value for ClientID as NULL. From front end, user will choose either for 'All Clients' or 'Particular Client' and 'For All Accounts' or 'For Particular Account. In table, clientID and account is will never be null. If there are multiple transactions to parent, it should return all the detail transactions related to that account for the date range. If I don’t it becomes partial processing. I have to process whole transaction as 1.

Many other filter are there.īut I want all transactions related to that Account. = IS NULL OR DepositAccounts.AccountID = daterange etc. From Deposit Inner Join DepositAccounts on Deposit.DepositID = DepositAccounts.DepositID Particular client and account is chosen from dropdown and submit button is clicked which runs another stored procedure pulls only transaction related to that account for that daterange.Įg: if account 1111 is chosen, then stored procedure is pulling only transactions related to 1111.If they want to see details, then clicking on link takes them to details page.ĭeposit page has various filters like client, Account and date range. When User loads ‘Deposit’ page, We show deposit table trans in the grid and provide a link.

I simplified the tables.įrom front end we show the transactions to the user.
