Najeeb Siddiqui wrote: Dear Team CB,
Is there a way to issue items to a customer on a trial Basis (Client  Approval / Client Check on Site ), let us say that the customer wants to check the item Specs at the installation site or wants to make sure that it is a 100% fit in terms of installation at his/her Property and wants to take the items out of our store. Is there a way to issue a document to acknowledge this.

We usually create a Hand Written Note for this purpose, is there a way to do that in CB .   in Certain software this function is called ( Material Supply for  Approval ) 

My suggestion would be to follow this procedure:

(1) Invoice the customer with future payment due terms (name could be "Material Approval") or the Source field could be set to "Material Approval" or a custom field could be added.  In case they don't bring the material back, they need to pay for it.

(2) Issue an RMA which you can use for tracking if they bring it back or not.  If they bring it back, you can process the RMA and credit.  If they don't bring it back, you can void the RMA.

David Nelson
Dynamic Enterprise Technologies Inc
Connected Business Partner
Seattle Washington USA

Read More...

Najeeb Siddiqui wrote: When editing / adding the Payment terms, the system issues a start date ( Current Date ) can this be changed to a previous date if not why so?

The date you are looking it is the create date of the payment term.  It does not let you change that date.  (My guess is there is/was a future plan to make that date the "effective date" but the plan has not been implemented yet)

Najeeb Siddiqui wrote: What do we need to do to upgrade the payment terms of existing customers from let's say 45Days to 30 days? I have added a couple of different payment terms but they are not shown in the individual customer information ... only the ones which were there when the customer was created are shown in the drop-down menu .. 

Under Banking / Setup / Payment, there is "term" and "group".  The "Term" is all possible payment terms.  The "group" are groups of payment terms which you can assign to customers.

It seems you added a payment term, but you did not add that payment term to the payment group connected to the customer you are looking it.

Be aware the payment term group setting is under the customer Ship-To setup tab, as each different Ship-To could have a different payment terms group.

David Nelson
Dynamic Enterprise Technologies Inc
Seattle | Portland | Los Angeles
www.dynenttech.com

Read More...

POINT 1:
You can have multiple suppliers per item.  In the item, there is a Costing tab.  In that tab, you can list all of the possible suppliers for an item.

POINT 2:
In Supplier preferences, there is an option "Filter items according to suppler".  If you turn this off, on a Purchase Order, the list of items will not be limited to the current supplier.

David Nelson
Dynamic Enterprise Technologies Inc
Seattle | Portland | Los Angeles
www.dynenttech.com

Read More...

Najeeb Siddiqui wrote: Dear CB Community,
 What Format would be the best choice, Usually we receive these PO's in PDF format Ranging From 250Kb to 350 KB depending on different factors. My concerns are as follows 
 

I would suggest attaching the file in whatever format you receive it in.  It will take time to convert the format.

Najeeb Siddiqui wrote: Dear CB Community,
1) Can We limit the file sizes to a certain Size so users don't accidentally attach large files?
 

I am not aware of a limit you can set in the CB software.  It would be possible to add a customization to set a limit.

Najeeb Siddiqui wrote: Dear CB Community,
2) Is there a place within CB where I can check my Attached File details and DB Size to check for any irregularities?

You can easiy query SQL server for this information.

Najeeb Siddiqui wrote: Dear CB Community,
4) is there any automated or efficient way of doing this?

Yes.  We can schedule a SQL query to email you when (a) there is an attachment over a certain size (b) your attachments grow in total over a certain size (c) your database grows to a certain size.  We can also purge attachments after a certain period of time to keep the size of your database down.

Najeeb Siddiqui wrote: Dear CB Community,
3) Are there any considerations i need to keep in mind while my users attach files ?

The primary consideration is size.  But if the attachments are important to your business, then I would not worry about the size much.  Disk space is not expensive.  However, (a) if you go over 10GB with the size of your database you can no longer use the free SQL Server Express Edition as it has 10GB limit (b) if you are doing backup to the cloud, it takes longer to backup a larger database.

David Nelson
Dynamic Enterprise Technologies Inc
Connected Business Partner
Seattle | Portland | Los Angeles
www.dynenttech.com

Read More...

Gary,

Woops.  I left one important word out of my previous post...unposted...let me clarify...

We need an unposted GRN VOID function.   (not delete GRN, not void GRN after posting)   From my understanding, an unposed GRN does not impacted any of the areas you listed in your previous post.

If is easy to accidentally create an unwanted unposted GRN from a PO.  Once created and not posted, you are stuck in a box.  At this point you are forced to post the unwanted GRN and then go through many undesired steps as outlined in my previous post. 

My customers do this on some regular basis, and I am the who has to go through the process of cleaning it up.  So that is why I'm plugged into this issue. 

David Nelson
Connected Business Channel Partner
Dynamic Enterprise Technologies Inc
Seattle Washington USA

Read More...

Jassim,

The basics are:
- Make sure your SQL server allows connections from other computers
- Make sure SQL server security is setup so the client computers can connect to SQL server
- In each client computer, in Connected Business, at the login prompt, create the connection to your database

It is somewhat hard to guide someone through the process via a message board as there are a number of pieces that must fix together.  If you want to join into a web meeting it would be easier.  If you want to schedule a web meeting with me, you can get my contact information from my web site, send an email, then we can schedule some time to meet.

David Nelson
www.dynenttech.com
Dynamic Enterprise Technologies Inc
Connected Business Channel Partner
Seattle Washington USA

Read More...

Najeeb,
 
I have a Canadian customer (not hosted by CB) using DD/MM/YYYY so I know it can work.
 
Are you running the CB client on your local workstation or on the CB hosted server?
 
At a minimum, the publicly visible reports can be changed to report the date in DD/MM/YYYY format.
 
If using RDP, your server login should be able to be changed so the format is DD/MM/YYYY (as date format is per login).
 
Worst case, you can host CB on your own server like Microsoft Azure so you can be in full control of the date format.
 
If you want to work with me and try to get the issue worked out, you can go to our web site for our contact information.
 
David Nelson
www.dynenttech.com
Dynamic Enterprise Technologies Inc
Connected Business Channel Partner
Seattle | Portland | Los Angeles

Read More...

Gary,
 
I studied the link you provided and otherwise looked into the issue.
 
Your statement “the date format is determined by the date format of the server” I think is technically incorrect.  SQL server doesn’t have a date format per se,as dates are not stored as strings on the database.  What SQL server does have is a “string to date” and “date to string” default conversion format. 
 
If an application is passing dates to SQL server as strings, it can cause problems on the SQL server side converting the strings to dates with different collations.  It is advised to not to pass dates in string format to SQL server for this reason.  If you send dates to SQL server using a date datatype, you are not going to have an issue with collation (because no string
to date data conversion takes place on the SQL server side).
 
You can read about the issue here and it explains how CB could be adjusted to not be dependent on SQL server collation:
 
stackoverflow.com/questions/27011693/whi...ault-datetime-format
 
If you must send dates to SQL server in string format,you could check the collation of the SQL server you are connected to, and the date format of the client, then format the dates in the correct format in the string you send to SQL server so the “string to date” conversion on the server side will work as expected.  In this way it would make the client date format and SQL server "string to date" format independent and the issue would be resolved.
 
David Nelson
Dynamic Enterprise Technologies Inc
Connected Business Channel Partner
Seattle | Portland | Los Angeles

Read More...

Gary,

The problem is with an accidentally or incorrectly created GRN from a PO. Once the GRN is created (and not yet posted), you a have a big problem on your hands. There is no VOID function available for the GRN.

The only way out of this situation is a painful process as noted in Michelle's post. You must post the unwanted GRN, create an unwanted Bill, post the unwanted Bill, create an unwanted return, post the unwanted return, create an unwanted debit memo, and post the unwanted debit memo. Not to mention the fact that your PO is now completed and you can't create a new and proper GRN from it when you are ready, so you also have to create a new PO.

We need a GRN VOID function.

The warehouse can be a fast paced place and it is easy for the warehouse staff to click the wrong button.

Given that we are forced to post unwanted GRNs, to keep the records as clean as possible, when I have a large GRN in this situation, I set the qty received to zero for all line items except he first line item, then set the first line item quantity received to 1.. This minimizes the items, the value, and the quantity of all the unwanted transactions you must process to get out of the situation.

David Nelson
Dynamic Enterprise Technologies Inc
Connected Business Channel Partner
Seattle | Portland | Los Angeles

Read More...

Most likely the problem is the SQL server on Machine1 is not configured to allow connections from other computers on the network (this is the default). Or it could be the firewall on Machine1 is blocking the SQL server port. My company would be happy to assist you in getting the workstations up and running. If you need our assistance, please email This email address is being protected from spambots. You need JavaScript enabled to view it. with your request and we can schedule time to assist.

David Nelson
CB Channel Partner
Dynamic Enterprise Technologies Inc
www.dynenttech.com

Read More...