Data Object Frequently Asked Questions (FAQ)

Do I Need to Know How to Code to Create a Data Object? #

The simple answer is, “No”. Data Objects are built using a no-code (i.e., point-and-click) environment. The closest a user might come to actual ‘programming’ while creating a Data Object would be if there is any conditional logic or filters—but even then, the user can utilize the familiar ‘point-and-click’ method to create any specialized logic.

What Naming Conventions Should We Use for Data Objects? #

When it comes to naming a Data Object (or, for that matter, any content in Assette) it is best practice to choose a standardized naming convention that is to be used throughout the entire organization that is functional and descriptive. Choosing one of the following common naming conventions. Data Object may only use letters (either upper or lowercase), numbers, hyphens or underscores in the name.

• Camel Case
  • First letter of every word is capitalized with no spaces or symbols between words.
  • Examples: UserAccount, FedEx, WordPerfect. A variation common in programming is to start with a lower case: iPad, eBay, fileName, userAccount.
    
• Pascal Case
  • Popularized by Pascal programming language, this is a subset of Camel Case where the word starts with uppercase. Thus, UserAccount is in Pascal Case but not userAccount.
    
• Snake Case
  • Words within phrases or compound words are separated with an underscore.
  • Examples: first_name, error_message, account_balance

Can Multiple Data Objects Have the Same Name? #

Data Objects, as with all other content in Assette, must have a unique name—though names may be shared across content type (e.g., two Data Objects cannot have the same name but a Data Object and a Data Block many share a common name).

While it is possible to have shared names between content, it is not suggested (e.g., a Data Object and Data Block named “Performance”) as this may cause unnecessary confusion. Assette recommends that names be both functional and descriptive.

Can I Name a Data Object “New”, “Old”, or “Test”? #

Yes, you can name the Data Objects as you see fit, however Assette recommends that Data Objects remain descriptive and functional names. Assette also recommends that if users must create such Data Objects that they are renamed or removed as soon as practicable.

How Do Users Distinguish Between Functionally Identical Data Objects? #

Sometimes it’s impossible to avoid having to create a Data Object with nearly identical functionality as an existing Data Object. In this case, Assette suggests using adding an extra adjective to the name to help differentiate the two. Assette highly suggests that the “Description” field be utilized in the Data Object’s General Info tab, specifically for this reason.

This scenario is most frequently seen when a table is shown transposed, in this case Assette recommends simply adding “_transposed” at the end of the Data Object’s name.

Can Users Search for Data Objects in the Authoring or Output Center by Name? #

No, users can only search for a specific Data Object by name directly in the Data Object Editor. However, users can view the Data Objects that are used in a Smart Shell or Smart Page using Assette’s X-Ray feature.

User will also see the Data Object’s Display Name (as opposed to the programmatic name) when creating Smart Shell and Smart Pages within the Assette PowerPoint Editor.

I Accidentally Deleted a Data Object, Can I Restore it? #

Yes, users can email the Assette Client Service Team to restore the deleted the Data Object. Please be sure to include the name of the deleted Data Object or other identifying information. Additionally, users are prohibited from deleting any Data Objects that are used by other content.

Can Users Share or Save a Data Object Search Filter? #

Data Object search filters cannot be saved or shared.

What Happens if I Change a Data Object’s Columns Name? #

Changing the Column Name of a Data Object may cause the Data Object to no longer function as expected or may require the Smart Shell to be remapped. This happens because the Smart Shell and Data Object use the Column Name as a key. Changing the display name of the column is fine.