I tried selecting all different combinations of entities, including only system entities, only custom entites, a single system entity, and a single custom entity.

As I have global admin I do not think it is a permissions issue.
related error log below:

System.ArgumentNullException: Value cannot be null.
Parameter name: source
at System.Linq.Enumerable.Where[TSource](IEnumerable1 source, Func2 predicate)
at Rappen.XTB.LCG.CSharpUtils.GetRelationships(EntityMetadataProxy entitymetadata, List1 includedentities, Settings settings) at Rappen.XTB.LCG.CSharpUtils.GetClass(List1 selectedentities, EntityMetadataProxy entitymetadata, EntityMetadataProxy commonentity, Settings settings)
at Rappen.XTB.LCG.CSharpUtils.GenerateClasses(List`1 entitiesmetadata, Settings settings, IConstantFileWriter fileWriter)
at Rappen.XTB.LCG.LCG.btnGenerate_Click(Object sender, EventArgs e)
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripButton.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

For UI, not file generation.

Currently all relationships are created as 1:N with the parent entity first, regardless of which entity you include the relationship from.
By respecting "originating" entity it would be possible to affect the layout of the diagram.

Selecting a combination of configuration in each of the 3 sections (Entities, Attributes, Relationships) that result in no rows leaves the grid with no header text and is visually not very nice.

Invalid path etc causes XTB to explode.
Handle more delicately.

When using DisplayName identifiers, duplicates may occur.
Make sure it doesn't.

Can we run this from the command line and if not, would you accept a PR along these lines?

Something like a console app or powershell script that can be run via a build process or directly from Visual Studio.

This would need to:

• accept configuration values, perhaps from a config.json
• consume config and output file(s) using CSharpUtils.GenerateClasses to ensure output is consistent with the GUI

With "Check all visible attributes when checking an entity" selected.
Behavior:
Sometimes when selecting an entity the attributes of the entity are checked and sometimes not.

If I follow the steps below then the result is not what I expect.

Steps:

1. Tick the Check all visible when checking an entity in Attributes section
2. Select to only should custom attributes
3. Tick account entity
4. Note the customised attributes appear and they are ticked
5. Select all attributes
6. Note the attributes all appear again and are ticked

I would expect that all attributes appear again but only the previously ticked, custom, attributes are still ticked.

Maybe I missed this feature: Is there a way to generate a constant for the "pseudo" Attribute owninguser?

As in the subject.

Reproducible Steps:

1. Change settings and select a solution
2. Save project
3. Change settings again and select a different solution
4. Load the saved project

The result is the last solution selected is the one that remains selected.

The method applying selection always reloads default settings file, even after loading settings from specific file.

Hi there,

This is a feature request. I couldn't find a way to generate entity plural name. It is useful when simply adding an "s" at the end of an EntityName will not work. For example, the plural for policy is policies.

Thanks.

If OutputFolder for a project is stored as a path relative to the project (configuration) file it would support distributed environments a lot better.

• Deployment: Online
• DB Version: 9.1.0.16843
• XTB Version: 1.2020.4.38
• Tool Version: 1.2020.2.1

For readability, add regions to generated code.

A checkbox in the options section that will toggle visibility of the legend entity.

When mutilple remarks lines are generated in the XML documentation, the /// is missing.

    public const string PrimaryKey = "cint_mms_res_subledger_rowid";
    /// <summary>Type: String, RequiredLevel: None, MaxLength: 100, Format: Text</summary>
    /// <remarks>Anger namn på händelsen, sätts vid skapande om namn är tomt.
    Namngivningsregel: Tidsstämpel - artikelnummer.
    Tidsstämpelformat: YYMMDDhhmmssffff (från UTC-tid när transaktion skapas).</remarks>

There are APIs to the PlantUML functionality generating the diagrams.
Would be awesome to have that within the tool.
See e.g. https://github.com/KevReed/PlantUml.Net

Add possibility to specify custom prefix and suffix to constant names.
No UI at this point, but possible to edit in the settings file.

CamelCasing function that identifies word parts breaks Account while identifying Count and turns it into AcCount.
Fix it.

Checked Include intersect but output file doesn't contain any intersect entities.

Prompt user to open generated file after it has been saved.

• Deployment: Online
• DB Version: 9.1.0.12056
• XTB Version: 1.2020.131.378
• Tool Version: 1.2020.1.3

Add constants for M:M-relationships.
Related to #16.

Here my configuration:

Output:

    public static class Contact
    {
        public const string EntityName = "contact";
        public const string EntityCollectionName = "contacts";
        public const string PrimaryKey = "address1_addressid";
        public const string PrimaryName = "fullname";

https://www.screencast.com/t/OTRpn2pzRe

When checkbox Check all visible attributes when checking an entity is checked, the selected entity is not checked, and you check an attribute, this cascades so the entity is checked which causes all attributes to be checked.

Option to compose constants with camel case, based on logical name.
new_shoe_size = ShoeSize
parentcustomerid = ParentCustomerId
new_incident_type_id = IncidentTypeId

These easily obscure the model if all are included.
Make it easy to exclude them.

• Deployment: OnPremise
• DB Version: 8.1.1.1005
• XTB Version: 1.2020.2.37
• Tool Version: 1.2020.2.1

It would be very convenient if the project configuration was stored with the actual output file.
Could be included as a comment on the last line or similar.

• Deployment: Online
• DB Version: 9.1.0.16843
• XTB Version: 1.2020.4.38
• Tool Version: 1.2020.2.1

When I select the contact or account entity, there are no address fields in the available attributes.

Opportunity Close entity has two optionsets with display name Status Reason, leading to two enums with same name.
Dedupe them!

importsequencenumber, createdon, ownerid, etc etc

Implement constant generation for global optionsets.

I would expect that if I untick the entity then the related attributes that are ticked would be unticked also, this does not appear to be the case.

Add the possibility to include static texts to the generated file.
For example you might want a static file with rectangle definitions boxing entities together in the model.
That could be accomplished by either adding the line:

!include EntityBoxes.plantuml

if you have a local file defining the rectangles in the same folder, or by including the rectangles directly as static text:

rectangle Geography #LightBlue {
    entity jr_City
    entity jr_Municipality
    entity jr_County
    entity jr_PostalCode
}

rectangle Types #Silver {
    entity jr_ParentCategory
    entity jr_Category
    entity jr_Type
}

• Deployment: Online
• DB Version: 9.1.0.16541
• XTB Version: 1.2020.4.38
• Tool Version: 1.2020.2.1

The form is cluttered by all the options (and some are still only available through editing the file).
Move them to a separate options dialog.

Remove empty summary tags in output file.

When starting the tool and before loading the entities the Project toolbar menu is clickable but the Load project... and Save project... options are disabled. I would expect either the toolbar menu to be disabled or the load project option to be enabled.

Suggestion: Include Relationship names in the generated constants.

Relationship relationship = new Relationship(CrmConstants.account.account_primary_contact);
_service.Associate(Contact.EntityName, contactId, relationship, relatedAccountReferences);

This improvement would remove the need to "magic string" the relationship name when instantiating Relationships to be used in Associate calls.

Some words are "broken" by current camel casing, need a list of exclusions from the work list.
E.g. "Country" is camel cased "CountRy" since it identifies "Count" as a valid word.

• Deployment: Online
• DB Version: 9.1.0.13836
• XTB Version: 1.2020.2.37
• Tool Version: 1.2020.2.1

Make the default templates for the generated classes possible to customize.

Sometimes you want to be able to strip away multiple different prefixes from logical and schema names.

The deduplication routine breaks when comments are applied to properties. Splitting on the '=' assumes everything to the left would be the same but the comments can differ. Pull request coming.

Adding correctly formatted tripple slash comments would add usability by sypplying code insigts.
Should contain CRM attribute type, max length, min/max value, format, cascade behavior etc.

Hello,

This plugin works absolutely perfectly with our CRM 2016 instances.
However, when I attempt to load the entities when connected to our of our CRM 2011 instances I receive an error which simply reads "Unable to evaluate query"?

Is there a potential fix for this?

I'm happy to provide some more information if it is needed.

Thanks!

They do something, but not what they should do.

When opening a project that contains entities that do not exist in connected organization, teh tool explodes.
Show a nice message instead.

• Deployment: Online
• DB Version: 9.1.0.14440
• XTB Version: 1.2020.2.37
• Tool Version: 1.2020.2.1

Attributes like createdon, importsequencenumber etc may very well be added to a separate generic common class instead of included in each individual entity.