The docs on IPP for the QBO Customer entity
Online Docs for QBO
indicate that Name is "Required". However, those same docs say "...if the FullName is not specified, then GivenName, MiddleName, and FamilyName are concatenated and used for the value of this field." Does this mean that if we query for Customers we can always expect to find a non-null "Name" field, or does it mean that we might get a null "Name" but should use the concatenation mentioned in its stead? Same question for Vendors? Thanks for any help you can provide.
Norman,
The Name will always be populated. Either you specify the name OR you specify the Given and Family name and it populates the Name field with those values.
Try this example. Login to QuickBooks online, enter the first, middle and last, then the display name populates automatically.
Here is the XML example when I only enter First Name, Last Name
<Name>Jazz, Hugo</Name>
<WebSite/>
<Email/>
<GivenName>Hugo</GivenName>
<MiddleName>J</MiddleName>
<FamilyName>Jazz</FamilyName>
regards,
Jarred
Related
This relates to Custom Fields in NetSuite.
I have added a List/Record field to Customer records, with the list type "Addressbook".
If you edit this field on a Customer record, it will give you a list of ALL Addresses, not just the ones relating to that specific Customer.
I cannot find a way get the field filtering options to limit the list to the specific record I am editing.
NOTE: Changing the List/Record list type to "Address" will provide no values at all.
Thanks in advance for your help!
I have sugarCRM 6.5.20 OnDemand. I am in the Studio. I have a 1:1 relationship from Leads to Leads. I am trying to get the Primary Email address of the related Lead and display it in a calculated field.
It seems like the calculated field formula should look like:
related($emails,"email1")
When I do that I get the following error:
Invalid formula: related: Unknown Field : email1
The dropdown list doesn't list the email at all. How can I get the email? All of my web searches have proven ineffective.
Update:
I am willing to make the calculated field be the primary email address of the current lead. To do that I found 2 variables named $email_addresses and $email_addresses_primary and $emails. There is also a function called valueAt.
I tried to use valueAt(1,$emails) and valueAt(1,$email_addresses)
The validator accepted the syntax but the value was always empty.
Can I make a calculated field off of the leads primary email?
You won't get the Email field for the Studio's formula calculation. Email field is stored in a separate table and not in the module's table. It is just put in the Layout along with the other fields of the module, but it is not the same as other fields. All the Email Addresses irrespective of the modules are stored together in the email_addresses table and are related to respective module records in the email_addr_bean_rel.
A www form provides my cgi script with a full name for the credit card information. The PayPal Rest API wants a first_name and last_name. If there are more than two 'words' in the full name, then what is the way to submit the information? I want to avoid declined cc payments.
Say, given
full_name="Mr. I M Testy".
Should I submit
first_name="Mr. I M",
last_name="Testy"
Or what?
Where is the guidance on the Paypal rest documentation?
The solution that seems to work best, in the sandbox, is to split the words given for card holder name into last name and everything else.
ex. "John Jacob Jingleheimer Schmidt" would be split into
last_name: 'Schmidt'
first_name: 'John Jacob Jingleheimer'
And that is how I would submit it. If the cardholder goes by one name that is the last name and I submit no first_name parameter at all.
You can either add them to the end of the first name as you are doing or before last name. There is no convention that is enforced via REST APIs. So as long as you are consistent on your end about how you handle names, the APIs should not stand in your way.
According to the documentation, there is a Business Rule for Vendor and Employee that says
The name, first name, or last name field should not be blank.
Considering that NAME is required for create, the question is ¿Does this mean that ALL three properties have to have a value on Create?
We understood that, so we ran some tests. Creating a record with the three properties populated has no problem. The issue comes when we try so insert a null value for GivenName and FamilyName (first name and last name).
Quickbooks seems to take the NULL values as valid, and when inserting the record is not returning any error. The problem is that the record that was inserted never shows in the QBD UI, but is seems like it persists somewhere, because if we try to insert it again we get a "duplicate name" error.
Not sure if this is an issue or an expected behaviour... Any hints??
Thanks
QuickBooks for windows has some legacy behavior to be aware of. The First, Last and Name combines for a unique identifier accross Customers, Vendors and Employees. So you should fill in ALL the information you have. Any attempts to insert a record with the same F or L name, will fail if there is a Customer, Vendor or Employee with the same F & L.
Second, you mentioned that the record doesn't show in QuickBooks for Windows?
Did it sync successfully? Did you check the error state of the record you inserted?
Did you look at the sync logs to see if it failed to sync?
Lastly, you need to check all three objects for a user with the same F & L name if you are getting a duplicate error. Normally you would check to see if the customer/vendor/employee exists firsts so you can update the existing or determine if it is in fact a new record.
hope that helps
Jarred
Sometimes when requesting users via Graph API, the objects returned are missing either the "first_name" or the "last_name" key/value pairs.
I haven't quite been able to find the pattern. Most of the time it's the "last_name" that is missing, but sometimes it's the "first_name". The "name" field typically contains what looks like a valid "[first_name] [last_name]" pair. Sometimes when the "last_name" is missing, "first_name" contains the same value as "name". Other times the value appears to be what you'd expect the "first_name" value to be based on the value of "name".
This happens for regular users (not test, which was apparently reported as bug in the past) and for a variety of locales (including en_US).
When is the first_name and/or last_name not available when requesting users from the Graph API?
Update:
Investigating this further, I noticed that occasionally what appears to be the last name is provided in the "middle_name" field instead. The registration form does not ask for a middle name, but looking at account settings I can see that one can provide an optional middle name, although the last_name is still required.
Does anyone have any feedback about whether this is a bug or if I'm running into old data that did not meet the same restrictions that are currently in place?
Try running this query: fql?q=select name,first_name,last_name from user where uid in (select uid2 from friend where uid1=me()) order by name I have friends from various parts of the world and not one of them are missing first or last.