Archive
BulkData GetBulkContacts Method
Retrieves the list of contacts, created at the organization, up to 96 hours in the past. This will retrieve all contacts on an account. Empty fields will not be returned.
Parameters
Name | Data Type | Is Required |
---|---|---|
OrgID | Long | Required |
Description | The organization’s ID number. | |
BeginDate | DateTime | Required |
Description | The beginning date of the date range for which to pull the list of new contacts. This date cannot be more then 96 hours in the past. | |
EndDate | DateTime | Optional |
Description | The end date of the date range for which to pull the list of new contacts. This will default to SYSDATE if left undefined. |
Returned Parameters
Name | Data Type |
---|---|
CONTACT_ID | Long |
Description | The contact’s ID number. |
ACCOUNT_ID | Long |
Description | The account’s ID number. |
ACCOUNT_NAME | String |
Description | The name on the account. This may differ from the primary contact in some instances. |
FIRST_NAME | String |
Description | The contact’s first name. |
LAST_NAME | String |
Description | The contact’s last name. |
KNOWN_AS | String |
Description | The name by which the customer prefers to be called. |
CONTACT_TYPE_NUM | Integer |
Description | The numeric value of the contact type. Available values:
|
CONTACT_TYPE_VAL | String |
Description | The textual value of the contact type. Available values:
|
EMPLOYER | String |
Description | The customer’s current employer. |
ACTIVE | Boolean |
Description | Indicates if the contact is active (“True”) or not (“False”). |
String | |
Description | The contact’s email address. This is the customer’s username if eStore/eCommerce are supported. |
ECOMM_CODE | String |
Description | No longer returned. |
FLEX_01 | String |
Description | A custom field, set up by the organization, designed to hold additional contact information. This is not displayed in the Store application. |
FLEX_02 | String |
Description | A custom field, set up by the organization, designed to hold additional contact information. This is not displayed in the Store application. |
FLEX_03 | String |
Description | A custom field, set up by the organization, designed to hold additional contact information. This is not displayed in the Store application. |
FLEX_04 | String |
Description | A custom field, set up by the organization, designed to hold additional contact information. This is not displayed in the Store application. |
FLEX_05 | String |
Description | A custom field, set up by the organization, designed to hold additional contact information. This is not displayed in the Store application. |
CREATED_DATE | DateTime |
Description | The date the contact was created. |
CREATED_BY_ID | Long |
Description | The user’s ID that created the contact. |
CREATED_BY_NAME | String |
Description | The first and last name of the user that created the contact. |
UPDATED_DATE | DateTime |
Description | The date the contact was last updated. |
UPDATED_BY_ID | Long |
Description | The user’s ID that last updated the contact. |
UPDATED_BY_NAME | String |
Description | The user’s first and last name that last updated the contact. |
ORG_ID | Long |
Description | The organizations ID number. |
Example
We’ll assume you’ve got a web reference, let’s name it BulkData, in your Visual Studio project. At this point we need to our objects. We’ll need the standard service object, a user request object and a data request object. We can define and create those like this:
// Create request and response objects
BulkData.LookupUser_Request user_request = new BulkData.LookupUser_Request();
BulkData.BulkDataSoapClient service = new BulkData.BulkDataSoapClient();
BulkData.BulkData_Request request = new BulkData.BulkData_Request();
Here’s my sample code of the Request and user objects.
// request
user_request.Username = "user";
user_request.Password = "pass";
user_request.Channel = 999;
request.OrgID = 123546;
request.BeginDate = DateTime.Today.AddDays(-1);
request.BeginDate = DateTime.Today;
Finally we can call the method and pass across the login object and the request object to perform our reservation. It’s a good idea to do this in a Try Catch block.
// Call the method that will load the response object
try
{
BulkData.BulkContacts_Response response;
response = service.GetBulkContacts(user_request, request);
}
catch (Exception ex)
{
MessageBox.Show(ex.Message);
}
Note that if something goes wrong the service will respond with an exception. You’ll want to take a look at that message returned in that exception so it can be debugged.
For a full list of methods, see BulkData Methods.
Workflow for Creating a Reservation or Rental
Entities
The following is a flow chart of the main entities involved in creating a rental or reservation in SWS.
An account can have multiple contacts and multiple rentals. A rental must have a primary contact (Contact Type = ACCOUNT_MANAGER) and can have additional secondary contacts. Site rules may require at least one secondary contact as well. A contact that is primary on one rental may be primary, secondary or not related at all to another rental on the account. The account name for personal accounts is the last name, first name of the first contact added to the account. For business accounts an account name should be specified. Each rental will be associated with the unit being rented. The unit has a number assigned by the organization and a primary key known as the UnitID. The two are often confused. If you are displaying information to a tenant you will generally want to use the Unit Number. If you are renting or adjusting a unit in code the unit ID, as the item’s primary key, is generally required.
Finding A Unit and Dynamic Pricing
The first step is displaying the available units. There are multiple options for this: GetSiteUnitData, GetSiteUnitDataV2, GetSiteUnitDataV3, GetUnitData and GetUnitDataWithPromos. GetUnitData returns ALL units in a site along with their pertinent information including ID’s and its version number which will be important when reserving the unit. This method allows a site to customize grouping, pricing and promos to their specifications. It means a little more work, but things will come out exactly how the organization prefers. The only required parameter is the SiteID, the rest of the parameters allow for filtering the results and are all optional. The GetSiteUnitData methods return a single unit based on a pre-set grouping. This grouping takes Width, Depth, Door, Climate, Access Type and Features values into account. For example, if you have ten 5X5 units, half that are climate controlled and half not, you will receive back, IF available, two units, one with climate control and one without. You also have the option to include the best available promotion for each item selected. Again, SiteID is the only required field. There are fewer filter options on this as the items have already been winnowed down. Also failing to indicate a desire for promos will default to false for performance purposes. Both methods return the information necessary to complete a reservation/create a new rental using the MakeReservation method.
Choosing an Account
For a brand new tenant, call CreateNewAccount. This method will create the account and at least one new contact, one new address and one new phone, which will then be available to accept rentals.
If you wish to add a unit to an existing customer’s account, you will need to use the SearchBy method to retrieve their AccountID and then use the AccountID to add the rental to their account.
Making a Reservation/Creating a New Rental
Once you have either created a new account or located an existing account, you can create a reservation/rental. First some terminology regarding reservations and rentals:
- Quote Only – This is created when a person has indicated interest in renting a unit but does not wish to commit to a reservation or rental. An account is still required. This allows for obtaining all the contact information. A unit is still required so anyone following up on the potential sale is aware of what type of rental the customer is looking for. The unit is NOT put on hold and can be rented at anytime by anyone else.
- Soft Reservation – This does not hold a specific unit, but will hold a unit of this type. The reservation will exist until its expiration date or until the reservation is cancelled. If there is only one unit left, it will not show as available to rent due to the soft reservation.
- Hard Reservation – This method holds a specific unit for a site specified length of time. Generally there is also a reservation deposit amount paid, although it is not required. If there is a deposit required, the payment process described below MUST be completed before the reservation process is considered complete. If it is not the rental will be cancelled during our nightly processing.
- Rental – To heck with reservations, the customer has a moving van parked out front. The move in is NOT done, however, until the payment process below has been completed.
MakeReservation does all of the above including upgrading from one status to another. MakeReservation will always return a QuoteID. If a reservation or rental is created there will also be a RentalID returned.
Making a Payment
So you’ve created the account and we’ve made our unit selection now we have to pay for the thing. Making a payment is a three step process.
Step One – GetAssessments – This method retrieves a list of line items to be paid. Regardless if this is a new or existing rental and whether or not you already know the total due this method MUST be called. Assessments may or may not be in existence for the rental. By calling this method it will create any assessments the organization or site requires. Failing to call this process means you may not have the correct total due and will cause errors in payment.
The method will return a list of line items that are due for the requested time-frame. If the tenant has any cash credit/escrow that can be used for payment, they will also be listed here. Note: Cash credit/escrow is not automatically deducted from the total due.
Step Two – GetTotalDue – This step can be skipped if the items in GetAssessments are looped through and totaled. There are some rules to keep in mind for this option. Extended is the total due not including taxes for the assessment, a fulfilled amount indicates some payment has been made on the assessment and that will not be deducted from extended, finally any tax amount must be added in. If a cash credit/escrow is present the extended amount indicates the available balance that can be used toward payment.
Step Three – MakePayment – And you thought we’d never get here. MakePayment accepts the above data, some total data and three payment types. One or any combination of payment types is allowed (i.e., customer wishes to pay half cash, half on a card, or possibly split the payment between two cards, etc.).
But, wait?! They have a promotion for the first month free and GetTotalDue says $0 is due. I don’t have to make a payment…. Yes, you do!!! Any new rental is not moved in until a payment is made. This will push the paid thru date forward and move the tenant in. If no payment is made, even if it’s a $0 cash payment, the rental will be ended as an abandoned rental during nightly processing. They will have to be moved in again, possibly missing out on a day of rent.
The MakePayment method will return a transaction ID if successful. The CashCreditApplied field has been deprecated.
ContactInfo Reference
Reference for any method using the ContactInfo object.
Name | DataType | Is Required |
---|---|---|
AccountID | Long | Ignored |
Description | The accounts system generated id. This is returned when you use the CreateNewAccount method or can be retrieved with the SearchBy method. | |
RentalID | Long | Ignored |
Description | The system generated id for the rental. This is returned when using the MakeReservation method or can be searched for using the SearchBy method. | |
ContactName | String | Required |
Description | The first and last name of the contact. | |
Address1 | String | Required |
Description | The first line of the address. | |
Address2 | String | Optional |
Description | The second line of the address. | |
City | String | Required |
Description | The city for the address. Max string length 50. | |
State | String | Required |
Description | The state/province for the address. Max string length 2. | |
PostalCode | String | Required |
Description | The ZIP/postal code for the address. Max string length of 15. | |
Country | String | Optional |
Description | The country for the address. Max string length of 25. |
SWS2 GetAccountInfo
Retrieves all the contacts for an account using either the account ID or the contact ID.
Parameters
Name | Data Type | Is Required |
---|---|---|
AcctID | Long | Optional* |
Description | The account’s ID number. This is returned when you use the CreateNewAccount method or can be retrieved with the SearchBy method. * Either AcctID or ContactID are required. |
|
ContactID | Long | Optional* |
Description | The rental contact’s ID number. This is returned when using the CreateNewAccount or AddNewContact methods or you can search for it using the SearchBy method. * Either AcctID or ContactID are required. |
|
SiteID | Long | Required |
Description | The site’s ID number. This can be found using the GetSiteList method. |
Returned Parameters
A custom field, set up by the organization, designed to hold additional account level information. This is displayed in the “Account Information” tab of the account in the Store application.
Name | Data Type |
---|---|
ACCT_ID | Long |
Description | The account’s ID number. This is returned when you use the CreateNewAccount method or can be retrieved with the SearchBy method. |
SITE_ID | Long |
Description | The site’s ID number. This can be found using the GetSiteList method. |
ACCT_NAME | String |
Description | The name on the account. This may differ from the primary contact’s name in some instances, such as a business account or a guardianship account. |
CFLEX01 | String |
Description | A custom field, set up by the organization, designed to hold additional account level information. This is displayed in the “Account Information” tab of the account in the Store application. |
CFLEX02 | String |
Description | A custom field, set up by the organization, designed to hold additional account level information. This is displayed in the “Account Information” tab of the account in the Store application. |
CFLEX03 | String |
Description | A custom field, set up by the organization, designed to hold additional account level information. This is displayed in the “Account Information” tab of the account in the Store application. |
CFLEX04 | String |
Description | A custom field, set up by the organization, designed to hold additional account level information. This is displayed in the “Account Information” tab of the account in the Store application. |
CFLEX05 | String |
Description | A custom field, set up by the organization, designed to hold additional account level information. This is displayed in the “Account Information” tab of the account in the Store application. |
ACCT_TYPE | String |
Description | Indicates the type of account, whether a company account or a customer account. |
ACCT_CLASS | String |
Description | Indicates if the account is a personal or business account class. |
CONTACT_ID | Long |
Description | The rental contact’s ID number. This is returned when using the CreateNewAccount or AddNewContact methods or you can search for it using the SearchBy method. |
FIRST_NAME | String |
Description | The first name of the primary contact. |
LAST_NAME | String |
Description | The last name of the primary contact. |
KNOWN_AS | String |
Description | The name by which the customer prefers to be called. |
ACTIVE | Boolean |
Description | Indicates if the account is active or not. |
CONTACT_TYPE | String |
Description | Indicates if the contact has full access or contact only status. |
CREATED_BY | Long |
Description | The user’s ID that created the account. |
UPDATED_BY | Long |
Description | The user’s ID that last updated the account. |
Example
We’ll assume you’ve got a web reference, let’s name it Store, in your Visual Studio project. At this point we need to reference our objects. We’ll need the standard service object, a GetAccountInfo_Request request object. You will also need to pass in credentials. We can define and create those like this:
// Create a request and response objects
StoreServiceClient client = new StoreServiceClient();
GetAccountInfo_Request request = new GetAccountInfo_Request();
As with every method we need to pass in credentials. We also set up the parameters for our request.
//Get Account Info setup
client.ChannelFactory.Credentials.UserName.UserName = "user";
client.ChannelFactory.Credentials.UserName.Password = "pass";
client.ChannelFactory.Credentials.SupportInteractive = true;
request.SiteID = 123456;
request.AcctID = 123456;
Finally we can call the method and pass across the login object and the request object to retrieve the data. It’s a good idea to do this in a Try Catch block.
try
{
// Call the method that will load the response object
System.Data.DataTable resp;
resp = client.GetAccountInfo(request);
}
catch (Exception ex)
{
MessageBox.Show(ex.Message);
}
Note that if something goes wrong the service will respond with an exception. You’ll want to take a look at that message returned in that exception so it can be debugged.
For a full list of methods see SWS2 Methods.