SuiteCloud Development Framework Flashcards

1
Q

SuiteApp Project Vs. Account Customisation, are both of these SuiteCloud projects?

A

Yes, they are both SuiteCloud Projects

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Account customization projects are intended for what?

A

Account customization projects are intended for customizations on accounts you own

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Can you lock objects in account customisation projects?

A

No. Locking objects is not supported in account customisation projects

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Can you configure account features in SuiteApp projects?

A

No. Configuring account features is not supported in SuiteApp projects

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Can we edit the custom transaction status from the NetSuite Account UI in SuiteApp projects?

A

Editing custom transaction status from the NetSuite Account UI is not allowed in SuiteApp projects

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

True or False?

We can hide files in Account Customisation projects.

A

False.

Hiding files is not supported in Account Customisation projects

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

True or False?

We can import Bundle Components in SuiteApp projects

A

False.

Importing Bundle Components is not supported in SuiteApp projects

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

True or False?

Importing files is not supported in SuiteApp projects

A

True

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Deleting files is not allowed in Account Customisation. However, what files CAN be deleted in SuiteApp customisations?

A

.js files can be deleted in SuiteApp customisations, but only .js files.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

True or false?

Deleting instances, objects and subrecords is not allowed in Account customisation projects

A

True

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What ARE SuiteApp projects?

A

SuiteApp projects are self-contained, standalone projects you can use to develop and deploy SDF SuiteApps to target NetSuite accounts

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Can you deploy SDF SuiteApps to NetSuite accounts you don’t own?

A

Yes, you can deploy SDF SuiteApps to accounts you might not own

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Using the Java CLI, what command do we use to create a SuiteCloud project?

A

“createproject”

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

When creating a SuiteCloud project through the Java CLI with the “createproject” command, what are the options/parameters for this command?

A

-type - Required
-overwrite - Optional
-parentdirectory - Required
-projectname - Required
-projectid - Required when type is specified as SUITEAPP
-projectversion - Required when type is specified as SUITEAPP
-publisherid - Required when type is specified as SUITEAPP

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Using the createproject command to create a SuiteCloud project through the Java CLI, one of the parameters is “Type”.

What are the 2 account types that can be set?

A

ACCOUNTCUSTOMIZATION or SUITEAPP

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Using the createproject command to create a SuiteCloud project through the Java CLI, one of the parameters is “Overwrite”.

What does this do?

A

Overwrite is a boolean (true or false flag) that indicates whether this new project will overwrite an existing project with an identical project name.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Using the createproject command to create a SuiteCloud project through the Java CLI, one of the parameters is “parentdirectory”.

What does this do?

A

Sets the parent directory of the project created.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

Using the createproject command to create a SuiteCloud project through the Java CLI, one of the parameters is “projectname “.

What does this do?

A

It’s a name for your project.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

Using the createproject command to create a SuiteCloud project with an account type of SUITEAPP through the Java CLI, one of the parameters is “projectid”.

What does this do?

A

A unique identifier to assign to the project.

This value must be a word with lowercase alphanumeric characters. It must be less than 40 characters

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

Using the createproject command to create a SuiteCloud project with an account type of SUITEAPP through the Java CLI, one of the parameters is “publisherid”.

What does this do?

A

The publisher ID of your SuiteApp project.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

Using the createproject command to create a SuiteCloud project with an account type of SUITEAPP through the Java CLI, one of the parameters is “projectversion”.

What does this do?

A

The version to assign to your project, using semantic versioning.

For example, specify the following project version if your SDF SuiteApp is version 1.02, minor revision #01242016.

1.02.01242016 <– Would look like this

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

When using the Java CLI to create a new project, it will always prompt you to enter an account password, unless you are using what?

A

Token based authentication

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
23
Q

Using the SuiteCloud CLI for Node.js, what command creates a new SuiteCloud project?

A

project:create

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
24
Q

When creating a SuiteCloud project through the SuiteCloud CLI for Node.js with the “project:create” command, what are the options/parameters for this command?

A

-i or –interactive - Optional
–type - Required
–overwrite - Optional
–projectname - Required
–projectid - Required when type is specified as SUITEAPP
–projectversion - Required when type is specified as SUITEAPP
–publisherid - Required when type is specified as SUITEAPP

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
Q

What does the -i or –interactive parameter do for the project:create command when creating a SuiteCloud project through the SuiteCloud CLI for Node.js.

What are the 2 commands not supported when using this parameter?

A

Runs the command in interactive mode.

-account:savetoken
-account:setup

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
26
Q

When creating a SuiteCloud project through the SuiteCloud CLI for Node.js and NOT running in interactive mode, what command must be used before working on the project?

A

-account:setup

27
Q

What 3 types of NEW forms can not be created using SDF?

A

New address, entry and transaction forms cannot be created using SDF

28
Q

What record type can we not create using SDF?

A

We cannot create integration records using SDF

29
Q

What must we do in order to work with forms in SDF?

A

We must import them from a NetSuite account

30
Q

What happens if we try to deploy SDF custom objects from an account customisation project if the objects are locked in the target NetSuite account?

A

We will not be able to deploy those SDF custom objects.

31
Q

What happens if we are trying to add a subrecord to a locked record type using an account customisation project?

A

We will not be able to add those subrecords to the locked record types.

32
Q

What is continuous integration?

A

An automated process that validates your SDF project before deploying it to a NetSuite account

33
Q

True or False?

Continuous integration does not allow human interaction

A

True

34
Q

True or False?

NetSuite offers Continuous Integration as a preparatory solution.

A

False.

This is not offered by Oracle NetSuite as a preparatory solution

35
Q

Continuous integration is only available for SDF projects and it only works for one of the CLI’s available for SDF. Which one?

A

It only works using SuiteCloud CLI for Node.js

36
Q

When using Continuous integration with the SuiteCloud CLI for Node.js, which option must you ensure your commands are NOT using?

A

Only use non-interactive commands

37
Q

True or False?

We must use a Continuous Integration 3rd party service provider

A

True, it is not provided by NetSuite

38
Q

When using Continuous integration, we must use a Version Control System that has what kind of strategy?

What is one primary example of such a Version Control System?

A

Must use a Version Control System with a Branching Model Strategy like GitHub

39
Q

Once employed, how does Continuous Integration function when committing and pushing changes to branches in your chosen Version Control System?

A

Makes it so when you commit and push changes to a specific branch, the project will be automatically tested through unit tests, validated, and deployed to your account

40
Q

True or False?

The automated actions you set up to be used with your Continuous Integration system can be set up using SuiteCloud CLI for Node.js

A

True

41
Q

You can set create different actions for each branch of your Version Control System.

What would be 2 prime examples of separate actions you could set up, assuming you have a development branch, and a production branch?

A

Can setup a dev branch that automatically deploys to a sandbox environment

Can setup a production branch that automatically deploys to production environment

42
Q

Any errors that occur when deploying through SDF will appear in 2 locations, what are they?

A

The errors will be displayed in the deployment and validation logs

43
Q

Regarding Deployment Logs:

You can review and download installation logs from the Deployment Audit Trail page of the NetSuite account (Customization > SuiteCloud Development)

What information will these logs include?

A
  • The objects and files that were installed
  • The date and time when objects and files were installed
  • Any warnings or errors that occurred during deployment
44
Q

SDF Validation logs perform server-side validation during two key processes, catching and logging the errors.

What are the two processes that this server-side validation occurs during?

A

The project deployment process and when deploying a SuiteCloud project to a target NetSuite account

45
Q

Regarding SDF;

There are 5 errors that may occur when working with Transaction Forms or Entry Forms.

What are they?

A
  • The object value is either invalid or does not exist in the account.
  • The field under the group is invalid
  • The property value of the object cannot be modified
  • The sameRowAsPrevious field must be set to false because it is the first entry
  • The object field must not be NOT_YET_SUPPORTED
46
Q

While deploying via SDF to a transaction or entry form, you have encountered the following error:

The object value is either invalid or does not exist in the account

What could be the cause?

A
  • The script ID value contains a typo
  • The script ID value does not exist in the target NetSuite account
47
Q

While deploying via SDF to a transaction or entry form, you have encountered the following error:

The field under the group is invalid

What could be the cause?

A
  • There is an invalid field name in the custom object.
    • Possibly a Typo
  • The field sequence is not in the correct order:
    • Unlike other SDF custom object types, form fields must follow the order as exported from the account
48
Q

While deploying via SDF to a transaction or entry form, you have encountered the following error:

The property value of the object cannot be modified

What could be the cause, and how can we fix it?

A
  • The property value is disabled or set to read-only in the target account

We should set the object’s property to match the default value used in the target account

49
Q

While deploying via SDF to a transaction or entry form, you have encountered the following error:

The sameRowAsPrevious field must be set to false because it is the first entry

How can we fix it?

A
  • The top and bottom position fields and the first field within a field group must be set as:

<SameRowAsPrevious>F</SameRowAsPrevious>

50
Q

While deploying via SDF to a transaction or entry form, you have encountered the following error:

The object field must not be NOT_YET_SUPPORTED

What could be the cause, and how can we fix it?

A
  • A custom template for the printing type was selected, but only standard templates are supported

Change the custom template to a standard template

51
Q

While deploying account configurations via SDF, you have encountered the following error:

Resolve the following conflicts to disable the feature

What could be the cause, and how can we fix it?

A

The feature specified is dependent on the state of more than one feature with a conflicting state

To fix it adjust the states of the features referenced in the error message.

52
Q

While deploying account configurations via SDF, you have encountered the following error:

Disable the dependent feature before disabling the feature

What could be the cause, and how can we fix it?

A

Cause: The feature is dependent on the state of another feature that is either enabled in the target account, or set to enabled in the account configuration

Solution #1
Disable the feature in the target account.

Solution #2
Set the feature to disabled in the AccountConfiguration/features.xml file in the project.

53
Q

While deploying account configurations via SDF, you have encountered the following error:

The feature must be enabled to deploy this project

What could be the cause, and how can we fix it?

A

Cause: The feature is set to ‘required’ in the manifest but also set to disabled in the account configuration

Solution #1:
Change the required state of the feature in the manifest file in the project.

Solution #2:
Set the feature to enabled in the AccountConfiguration/features.xml file in the project.

54
Q

While deploying account configurations via SDF, you have encountered the following error:

The feature is duplicated

What could be the cause, and how can we fix it?

A

Cause: There are multiple occurrences of the referenced feature ID

Solution:
Remove all the duplicates.

55
Q

While deploying account configurations via SDF, you have encountered the following error:

Enable the dependent feature before enabling the feature

What could be the cause, and how can we fix it?

A

Cause: The feature is dependent on the state of another feature that is either disabled in the target account, or set to disabled in the account configuration

Solution #1
Enable the feature in the target account.

Solution #2
Set the feature to enabled in the AccountConfiguration/features.xml file in the project.

56
Q

While deploying account configurations via SDF, you have encountered the following error:

The feature is missing its field

What could be the cause, and how can we fix it?

A

Cause: A feature entry in the account configuration is missing its ID field

Solution:
Add the missing field ID to the feature definition in the AccountConfiguration/features.xml file in the project.

57
Q

While deploying account configurations via SDF, you have encountered the following error:

The feature’s field requires a value

What could be the cause, and how can we fix it?

A

Cause: A feature entry in the account configuration is missing its field value

Solution
Add the missing field value to the feature definition in the AccountConfiguration/features.xml file in the project.

58
Q

While deploying account configurations via SDF, you have encountered the following error:

The feature is not available on this account

What could be the cause, and how can we fix it?

A

Cause: The feature is valid but does not exist in the target account

For example, you may have imported some features from a OneWorld account that are not available in other account types. This error occurs when you try to deploy a OneWorld account configuration to other account types.

Solution #1
Remove the referenced feature definition from the AccountConfiguration/features.xml file in the project so that you can deploy to the target account.

Solution #2
Only deploy the project to account types that support the referenced feature.

59
Q

While deploying account configurations via SDF, you have encountered the following error:

The configuration field from the feature is missing

What could be the cause, and how can we fix it?

A

Cause: A feature entry in the account configuration is missing a required field (that is the status field)

Solution
Add the missing field to the feature definition in the AccountConfiguration/features.xml file in the project.

60
Q

While deploying account configurations via SDF, you have encountered the following error:

Feature is not modifiable

What could be the cause, and how can we fix it?

A

Cause: There was an attempt to modify a feature (DOCUMENTS or SUITEAPPDEVELOPMENTFRAMEWORK) that SDF requires to function

Solution
Remove the reference to the feature definition in the AccountConfiguration/features.xml file in the project.

61
Q

While deploying account configurations via SDF, you have encountered the following error:

Feature(s) definition must start with tag but found tag

««««««««««««««««««««««««««
description would show like this:

Feature definition must start with the <tag_name> tag but found the <tag_name> tag.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>></tag_name></tag_name>

What could be the cause, and how can we fix it?

A

Cause: There was a typo or misspelling in the AccountConfiguration/features.xml file

Solution
Change the referenced tag to <feature> or <features>, depending on where the error occurred.</features></feature>

62
Q

While deploying account configurations via SDF, you have encountered the following error:

An invalid feature ID

What could be the cause, and how can we fix it?

A

Cause: There was a typo or misspelling in the AccountConfiguration/features.xml file

Solution
Remove the reference to the invalid ID in the AccountConfiguration/features.xml file in the project.

63
Q

While deploying account configurations via SDF, you have encountered the following error:

Is an invalid feature state

What could be the cause, and how can we fix it?

A

Cause: There was a typo or misspelling in the AccountConfiguration/features.xml file

Solution
Change the referenced feature state to ENABLED or DISABLED.

64
Q

While deploying account configurations via SDF, you have encountered the following error:

You cannot use SuiteCloud Development Framework to enable the feature because it requires a Terms of Service user agreement

What could be the cause, and how can we fix it?

A

Cause: There was an attempt to change the state of a feature that requires a Terms of Service user agreement

Solution
Remove the reference to the feature definition in the AccountConfiguration/features.xml file in the project.