JadeGit
DownloadsSource
0.14.0
0.14.0
  • Welcome
  • Developers
    • Getting Started
      • Repositories
      • Branches
      • Remotes
    • Making Changes
      • Adding Schemas
    • Deployments
      • Scripts
    • Platform Support
  • Troubleshooting
  • Deployment
    • Overview
    • Registry
  • Console
    • Overview
    • Install
      • Clone
      • Fetch
    • Open
      • Switch
    • Extract
      • Commit
      • Backfill
    • Registry
    • Build
  • Migration
    • Overview
Powered by GitBook
On this page
  • Change Tracking
  • Schema Versioning
  • Deployment
  • Commands
  • Multi-User Support
  1. Developers

Platform Support

PreviousScriptsNextTroubleshooting

Last updated 1 month ago

This page provides an overview of notable issues where support is limited due to Jade platform issues (raised via Parsys or ), or support hasn't been implemented within JadeGit yet.

Check the for other issues, where you can create new issues for faults or new feature requests for JadeGit in general (whether they should be noted here or not).

Change Tracking

The following table lists entity operations which cannot be supported during development due to issues with the or because support hasn't been implemented yet.

Entity Type
Function
Issue
Workaround
Hot Fix

References

Inverse Deletion

PAR 66873

Update references affected when change isn't tracked upfront.

Schemas

Deletion

PAR 68417

Delete schema file & folder from repository directly.

7

Forms

Schema Load

PAR 70027

Update forms via painter following schema load.

Controls

Change Type

Update property text after changing control type via painter.

Classes

Change Interface Mapping

Update class text after removing interface mapping.

Update existing methods after they're add/removed from interface mapping.

C# Exposures

Add & Update

PAR 67309

None

External Databases

Update

Not Raised Yet

None

Skins

Any

Deploy changes directly.

Entity Type
Function
Issue
Workaround
Hot Fix

Local Features (on imported classes)

Any

PAR 69387

None

References

Inverse Deletion

PAR 66873

Update references affected when change isn't tracked upfront.

Translatable Strings

Deletion

PAR 68418

Remove from locale file within repository directly.

Schemas

Deletion

PAR 68417

Delete schema file & folder from repository directly.

39

Schemas

Update Text

PAR 67677

Update schema file within repository directly.

Forms

Schema Load

PAR 70027

Update forms via painter following schema load.

Controls

Change Type

Update property text after changing control type via painter.

Classes

Change Interface Mapping

Update class text after removing interface mapping.

Update existing methods after they're add/removed from interface mapping.

C# Exposures

Add & Update

PAR 67309

None

External Databases

Update

Not Raised Yet

None

Skins

Any

Deploy changes directly.

Entity Type
Function
Issue
Workaround

Local Features (on imported classes)

Any

PAR 69387

None

References

Inverse Deletion

PAR 66873

Update references affected when change isn't tracked upfront.

Translatable Strings

Deletion

PAR 68418

Remove from locale file within repository directly.

Schemas

Deletion

PAR 68417

Delete schema file & folder from repository directly.

Schemas

Update Text

PAR 67677

Update schema file within repository directly.

Forms

Schema Load

PAR 70027

Update forms via painter following schema load.

Controls

Change Type

Update property text after changing control type via painter.

Classes

Change Interface Mapping

Update class text after removing interface mapping.

Update existing methods after they're add/removed from interface mapping.

C# Exposures

Add & Update

PAR 67309

None

External Databases

Update

Not Raised Yet

None

Skins

Any

Deploy changes directly.

Schema Versioning

The following table lists issues with schema versioning during development which impacts accurate change tracking.

Issue
Problem
Workaround

PAR 67751

When an entity needs to be versioned during an update, change tracking cannot distinguish if the change is being made in current or latest schema version.

Explicitly version the schema, update entity text in latest schema version, then perform update or delete operation.

PAR 67678

When an entity is deleted from latest schema version, change tracking treats it as current schema version when latest entity version doesn't exist.

Update the entity in latest schema version first, then delete it.

Deployment

The following table lists issues which impact deployment capabilities.

Issue
Problem
Hot Fix

Cannot handle map file changes efficiently without intermediary re-orgs.

Complete JCF support needed to support rename & delete operations for all entity types.

PAR 70112

Cannot delete class in latest schema version due to subschema reference error.

7

Issue
Problem
Hot Fix

Cannot handle map file changes efficiently without intermediary re-orgs.

Complete JCF support needed to support rename & delete operations for all entity types.

PAR 66557

Cannot remove property after removing from exported package in latest schema version.

PAR 67022

Cannot delete interface in latest schema version due to deleted collection references.

39

PAR 70019

Cannot delete interface in latest schema version due to deleted implementors.

39

PAR 70112

Cannot delete class in latest schema version due to subschema reference error.

39

Issue
Problem

Cannot handle map file changes efficiently without intermediary re-orgs.

Complete JCF support needed to support rename & delete operations for all entity types.

PAR 66557

Cannot remove property after removing from exported package in latest schema version.

PAR 67022

Cannot delete interface in latest schema version due to deleted collection references.

PAR 70019

Cannot delete interface in latest schema version due to deleted implementors.

PAR 70112

Cannot delete class in latest schema version due to subschema reference error.

Commands

Command
2020 SP1
2022 SP2
2022 SP3

Delete Application

❌

✔

✔

Rename Application

❌

✔

✔

Delete Library

❌

✔

✔

Rename Library

❌

❌

❌

Rename Package

❌

✔

✔

Delete ExportedType

❌

✔

✔

Delete ExportedFeature

❌

✔

✔

Delete Exposure

❌

❌

✔

Delete HTMLDocument

❌

❌

❌

Rename HTMLDocument

❌

❌

❌

Delete RelationalView

❌

❌

❌

Rename RelationalView

❌

❌

❌

Multi-User Support

JadeGit currently supports development on a single-user Jade database only.

PAR 70191

PAR 70215

PAR 70191

PAR 70215

PAR 70191

PAR 70215

The following table shows what Jade versions support new JCF commands (proposed by ), using which deploying these kinds of changes is supported by JadeGit.

Support for multiple thin-client users connecting to a single-user application server depends on changes needed to retrieve .

Support for multiple users/nodes connecting to a database server depends on .

JEDI
project issue tracker
IDE hooks
JEDI #457
thin-client user configuration
JEDI #402
#153
#157
Not Implemented
#153
#157
Not Implemented
#153
#157
Not Implemented
JEDI #102
JEDI #457
JEDI #102
JEDI #457
JEDI #102
JEDI #457