AudienceVisibility Table (232)

• 2 minutes to read
 • 2 minutes to read

How projects (or whatever) should be made visible in audience

Fields

Name Description Type Null
AudienceVisibility_id Primary key PK
sourceTable Source table, only table 'project' valid in Audience for Six TableNumber
sourceRecord Record ID in source table. This is the record to be made visible RecordId
controllingTable The table that controls visibility of the source record TableNumber
controllingRecord The record in the controlling table that defines visibility of the source record RecordId
constraintEnabled If 1, this visibility constraint is enabled; otherwise it is there for the record, but not active Bool
comment A possible user comment String(254) ●
extraInfo Extra info value Id ●
registered Registered when UtcDateTime
registered_associate_id Registered by whom FK associate
updated Last updated when UtcDateTime
updated_associate_id Last updated by whom FK associate
updatedCount Number of updates made to this record UShort

AudienceVisibility table relationship diagram

Indexes

Fields Types Description
AudienceVisibility_id PK Clustered, Unique
sourceTable, sourceRecord TableNumber, RecordId Index
controllingTable, controllingRecord TableNumber, RecordId Index

Relationships

Table Description
associate Employees, resources and other users - except for External persons

Replication Flags

  • Replicate changes DOWN from central to satellites and travellers.
  • Replicate changes UP from satellites and travellers back to central.
  • Copy to satellite and travel prototypes.

Security Flags

  • No access control via user's Role.