Rise of The Ninja

[red1]

Now Ninja is improved for CSV importing to accept:
1. Commas in a field i.e. "Patio Fun, Inc"
2. Mixup Casing i.e. 'M_PRICELiST_id"
It will also now process BeforeSave and AfterSave of any model class if the dataset belongs to a present model particularly for core models such as C_BPartner and M_Product. This will result in Accounting Defaults created as expected. C_Order/Lines will also need less values such as PriceList.

[red1]

I have made a template Ninja Excel for any use here https://sourceforge.net/projects/red1/f ... leCreator/
(I be including a data-set to automatically Pack Out / Pack In your new data model!
Review and then Import Model the _4 and 05 sheets after GenerateModule of the imported model.).

You use this together with the blank plugin here https://bitbucket.org/red1/org.red1.blank

We all know it is always the very first part that is the steepest learning curve, so I be making a movie how to make the first baby steps from nothing. Hopefully from there you can follow and complete easily the whole series shown prior to this.

[red1]

ModelMaker.png (76.86 KiB) Viewed 6101 times

Notice the use of formula in cell to ensure correct typo. Spelling must be sharp and exact. Header column names are not case-sensitive as forced UPPERCASE will be used.

CodeMaker.png (69.84 KiB) Viewed 6101 times

PackOutDetail.png (90.55 KiB) Viewed 6101 times

Note how the CONCATENATE cell formula is used to good effect using other fields arbitrarily that has no effect during import into PackOut model. It be ready to export your 2Pack on the fly. Note that AD_Menu_ID look up expects your MenuName to be spaced before leading caps. You have to do that manually.

[red1]

Referring to https://groups.google.com/forum/#!topic ... Q2hUxwPFR0 ,
Dr Leonard Walletzky of Brno University in Czech Republic when using iDempiere and now Ninja for his classes, found a bug which is not a bug but a feature. You need not use D#Date Y#IsSumtin, Q#Qty if the prefix names already as such. Otherwise Ninja will parse it into D#D#DateSumtin.

Since he tested it via binary which i hardly do as i test fully from Eclipse source, while replicating his condition, I discovered a real bug that MField creation in the DocEvent validating of New MColumn and Changed MColumn doesn't work if the plugin is not refreshed each time. This is inconvenient and failure prone. So the best way is to bring such MField code into Ninja core process and i did that.

Enroute i made Ninja able to refresh changes to the Module Creator without falling back on previous backup for correcting mistakes such as 1. Column>Field.Name and 2.Adding DocAction structure to a freshly created model.

1. The Column>Field.Name can be changed repeatedly without concern of corruption because it is merely a change of the Window/Tab/Field.Name displayed without disturbing any column properties.

2. Basic model generation can be further regenerated with DocAction structure by checking the Workflow Structure box and then further for Kanban display. However such action cannot be reversed i.e. to delete back the additional properties. But you can hide its display in window and act as a basic model.

Next on my wish list is to make Ninja able to facilitate WebServices access to newly created data model on the fly.

[red1]