Difference between revisions of "Record Name"

From LongJump Support Wiki
imported>Aeric
imported>Aeric
 
(2 intermediate revisions by the same user not shown)
Line 8: Line 8:


Then  
Then  
:* It becomes possible to use <tt><nowiki>http://.../record/Customer/ABC Co</nowiki></tt> to access a Customer record,<br> as well as <tt><nowiki>http://.../record/Customer/12345</nowiki></tt>.<br>-and-
:* It becomes possible to use "<tt><nowiki>http://.../record/Customer/ABC Co</nowiki></tt>" to access a Customer record,<br> as well as "<tt><nowiki>http://.../record/Customer/12345</nowiki></tt>".<br>-and-
:* When you click the Copy Short URL icon [[File:CopyShortURL.png]] in the GUI while displaying the record, the URL you are given to copy is <tt><nowiki>http://.../record/Customer/ABC Co</nowiki></tt>.
:* When you click the Copy Short URL icon [[File:CopyShortURL.png]] in the GUI while displaying the record, the URL you are given to copy is "<tt><nowiki>http://.../record/Customer/ABC Co</nowiki></tt>".


;Considerations:
;Considerations:
:* {{Type}}s have a <tt>name</tt> field, but no Record Identifier. For those objects, creating a unique index on the <tt>name</tt> field creates a Record Name that is used in URLs.
:* Most {{Type}}s have a <tt>name</tt> field, but no Record Identifier. For those objects, creating a unique index on the <tt>name</tt> field creates a Record Name that is used in URLs.
:* One exception is [[Contacts]], which have neither a name <tt>name</tt> field nor a  Record Identifier. For those objects, it is not possible to define a Record Name. They can be accessed using a Record ID only.
:* One exception is [[Contacts]], which have neither a name <tt>name</tt> field nor a  Record Identifier. For those objects, it is not possible to define a Record Name. They can be accessed using a Record ID only.<noinclude>
<noinclude>


[[Category:Glossary]]
[[Category:Glossary]]
</noinclude>
</noinclude>

Latest revision as of 23:00, 28 December 2011

When you create an Index on an object, it is possible to specify the object's Record Identifier (declared in Record Locators) as the index field.

When the Index you create is unqiue, that value becomes the "name" of the record. That name is then and it can used as part of a Record URL you specify.

For example:

  • If the Record Identifier for the Customer object is specified as customer_name
    -and-
  • A unique Index is created on the Customer object, with Record Identifier chosen as the index field.

Then

  • It becomes possible to use "http://.../record/Customer/ABC Co" to access a Customer record,
    as well as "http://.../record/Customer/12345".
    -and-
  • When you click the Copy Short URL icon CopyShortURL.png in the GUI while displaying the record, the URL you are given to copy is "http://.../record/Customer/ABC Co".
Considerations
  • Most Built-in or CRM objects have a name field, but no Record Identifier. For those objects, creating a unique index on the name field creates a Record Name that is used in URLs.
  • One exception is Contacts, which have neither a name name field nor a Record Identifier. For those objects, it is not possible to define a Record Name. They can be accessed using a Record ID only.