Setup.json
Settings in the setup.json file
There are a lot of different settings that you can change per repository. Please always make a copy of the setup.json file and name this file setup_[Your Employee Shortcut].json. Do not change the settings in the original setup.json.
General Settings
Setting |
Description |
Example |
Name |
Name of the repository. The name is used in the sidebar list. |
acadon_timber |
Version |
The version setting is mainly used for tagging the commits in git. Furthermore it is shown in the sidebar repository list |
Maple |
RepoType |
The Repository Type is used to define which actions are available for the repository. At the moment the RepoTypes Solution, Customer and SolutionLegacy are supported. It is also possible to define your own custom RepoTypes |
Solution |
BusinessSolution |
|
|
NavVersion |
This setting is mainly used to find the correct Microsoft Tool Powershell Script. It is also used to open the correct DevClient |
BC1904 |
VersionCodeunitID |
ID of the Nav Version List Codeunit. This is used for the automatic versioning |
5041499 |
SolutionVersionNo |
|
|
Localizations |
The different Localizations that need to be updated |
[ "DE", "NL" ] |
DatabaseName |
Database name of your local Database. |
WOOD_140 |
DatabaseServer |
Your own database server. Should only be set in User Setup. |
AGI-NOTEBOOK |
TDatabaseName |
Database name on TSQL Server |
WOOD_140 |
TDatabaseServer |
TSQL Server Address |
TSQL\TIMBER |
TDirectory |
Folder on the network storage. In this directory the fob files will be saved |
\\tfile\Kunden\Branche Holz\14.0\ |
ReviewOpenBeyondCompare |
Set this setting to true if beyond compare should open automatically in the review process |
true |
OpenBeyondCompareAfterMerge |
Set this setting to true if beyond compare should open automatically in case that there is a merge conflict |
true |
CompileAfterImport |
Set this setting to true if the objects should be compiled after importing to the database |
true |
SyncAfterImport |
Set this setting to true if the scripts should automatically sync the database after import. There will be a question for an elevated command before every sync. |
true |
SaveObjectsBeforeRefresh |
With this setting you can define if the modified objects in the database should be saved before any refreshing. The objects are saved to the workspace folder in the repository |
true |
RunDevClientAsAdmin |
If you set this flag, the dev client will be opened in admin mode. There will be a question every time you start the dev client. |
true |
SharepointLink |
Link to the sharepoint page. This link can be opened in the sidebar. |
|
RepoCulture |
Set the export culture for the Repo. Default is de-DE |
en-US |
TExportWithTXTasZIP |
Export Objects as FOB and TXT and zip them. |
true |
SolutionNo |
Set the AUSTER Solution No. for the Repository. This is used to get a list of extensions for this solution. |
0067 |
%appdata%/adc Settings
These Settings have do be done in the Setup file in %appdata%/adc
Setting |
Description |
Example |
ClientPath |
Path to your DevZup Client Folder |
C:\DevZup\Client\ |
ServiceTierPath |
Path to your DevZup Service Tier Folder |
C:\DevZup\Service\ |
RepoPath |
Path to your Repository Folder. This is the path where the sidebar checks for repositories |
C:\GIT\ |
ScriptRepo |
Name of the Sidebar Repository. |
DevelopmentBuildAndDeploy |
DevOps Settings
Setting |
Description |
Example |
AzureDevOpsRepoId |
This is the internal ID of the DevOps Repository. Unfortunately there is currently no easy way of getting the ID. What you can do is the following. 1. Open the DevOps Repository in the browser. 2. Create a new Pull Request 3. Inspect the URL. There is a sourceRepositoryId |
7523cc0a-0768-418f-9fdb-bd0f93b230c8 |
AzureDevOpsProject |
Azure DevOps Project Name |
acadon_timber |
AzureDevOpsPAT |
Azure DevOps Personal Access Token. This has to be added to the %APPDATA%/adc setup. |
see here how to generate your DevOps Personal Access Token |
Docker Settings
Setting |
Description |
Example |
ContainerName |
The container name defines the base name for the container. If you create a container for a specific branch like bugfix, the branch type will be appended to the container name. |
maple |
BaseDockerImage |
Defines the base Docker Image. This image will be used for the Container |
mcr.microsoft.com/businesscentral/onprem:1904-rtm-de-ltsc2019 |
UseContainer |
This flag will be enabled automatically when a container is created |
true |
DockerMode |
Use Container, Net or External SQL Database |
ContainerDB, NetDB or ExternalDB |
Macro Settings
Setting |
Description |
Example |
ADCMacroPath |
Path where to save the ADC Macros |
|
MacroStopHotkey |
It is recommended to add this setting to the %APPDATA%/adc setup. This key will stop the macro skripts |
F12 |
Styleguide Settings
Setting |
Description |
Example |
CheckGuidelines |
Set this setting to true if you want to enable to the code styleguide check. |
true |
MandatoryLanguages |
The Languages that are checked in the style guide check |
[ "DEU", "ENU", "NLD" ] |
BranchSpecificSettings
It is possible to define Branch Specific Settings. This is done by following the following structure:
"BranchSpecificSettings": {
"branch": {
"settingName": "settingValue",
}
}
}
This could look like the following:
"BranchSpecificSettings": {
"master": {
"DatabaseName": "WOOD_140",
"ServiceTier": "WOOD_140"
},
"hotfix/*": {
"DatabaseName": "WOOD_140",
"ServiceTier": "WOOD_140"
},
"bugfix/*": {
"DatabaseName": "WOOD_140_INTREL",
"ServiceTier": "WOOD_140_INTREL"
},
"feature/*": {
"DatabaseName": "WOOD_140_INTREL",
"ServiceTier": "WOOD_140_INTREL"
}
}
}