Reading...
Play button
Play button
Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
8 Cards in this Set
- Front
- Back
|
What are different Names entities, attributes, and relationships can have?
|
Display name --The name that is displayed to the user
Display Collection Name A plural version of the display name. This only applies to entities. Logical Name The unique name of the entity or attribute. This name is all lowercase. If it is a custom entity, attribute or relationship, it has a prefix defined in the Organization.SchemaNamePrefix attribute. Schema Name The schema name is specified upon creation. It must be unique. It is used to create the logical name. This name should be in Pascal case. The schema name is used to create the class for the entity when using early bound programming. If it is a custom entity, attribute or relationship, it has a prefix defined in the Organization.SchemaNamePrefix attribute. |
|
|
What are the different actions an entity supports ?
|
Create
Creates a record of a specific entity type, including custom entities. Update Modifies the contents of a record. Delete Deletes a record. Retrieve Retrieves a record. Retrieve Multiple Retrieves a collection of records. Assign Changes ownership of a record. Share Grants or revokes access to a record to another user or team. Associate Creates links between a record and a collection of records where there is a relationship between the entities. Disassociate Removes links between a record and a collection of records where there is a relationship between the entities. |
|
|
Rules for Sharing Records ?
|
Anyone with share privileges on a record can share it with additional users or teams.
Anyone with share privileges on a record can set access rights for that record. These access rights control how a user who shares a record can access that record. Access on a shared record can be set to any access right, for example, read or write. Access rights on a shared record can be different for each user that the record is shared with. A record can be shared with the same security principal only one time. A user can share a record if they have share privileges on that record. Anyone with share privileges on a business record can modify the access rights for users who have the record shared. Anyone with share privileges on a business record can remove sharing for a specified user who has the record shared. Anyone with share privileges on a business record can remove sharing for all users with whom the record was previously shared. |
|
|
What are the different type of Entity ownership ?
|
Organization Owned
Contains data involving something that belongs to or that can be viewed by the whole organization. Organization-owned entities cannot be assigned or shared. For example, products are owned by the organization. These entities have an attribute named organizationid. Business Owned Entities that belong to a business unit. These entities have an attribute named owningbusinessunit. User or Team Owned Assigned to a user or to a team. These entities contain data that relates to customers, such as accounts or contacts. Security can be defined according to the business unit for the user or team. These entities have attributes named owningteam and owninguser. None These entities are not owned by another entity. |
|
|
What is Product Catalog ?
|
A product catalog is a collection of products with their pricing information
|
|
|
What is Price list ?
|
Price lists contain one to many individual product prices, aggregated together into a list for categorization purposes. This enables easier maintenance and usability of the list
|
|
|
What is Unit and unit group?
|
A unit is a measurement that specifies in what quantity a product will be sold. A unit group contains one to many types of unit of measurement, as calculated from a base unit. A product is tied to a unit group in which it is sold.
|
|
|
What is discount list
|
A discount list is an aggregation of different discounts, specifying how much of a discount the user can receive when the purchasing amount falls between certain ranges. Discount lists can exist at each quantity level, together with detail lines that contain the quantity breakpoints, and the reduction in the price.
|
