In order to decrease the view json size and remove redundant information, we may introduce the new idea. The case is when in the view or list are used same fields from the same entity multiple times. This case happens when there is a view with many N:N relations that are item to self, and also when in the record view - we use subviews in the sidebar from the same entity. What we can do as an idea:

in the record view json:

1. create new property in the meta object called => fields.
2. In meta.fields create unified object properties for each field by following this convention:
   • field from the same entity has the property name "field_name"
   • field from another entity has the property name "$entity_name$field_name
3. in the current field meta -> in the sidebar item or in the column item, instead of the whole "meta" object, include just -> "metaName" (similar to the already present dataName). this will serve as a way to get the real meta info when needed

It will be very suitable to be able to place a different icon for each view and list in the sitedabar of the record details screen.
In order to do that we will neede to extend the record view and list elements with a text property icon_name.

Please extend the API to support 1:N Relation field filter ability. On UI it is implemented

Add new default value option "GenerateNewID", which should be required when switching from non unique to unique type of field.

When selected and no value is provided for unique field new GUID should be generated as value.

All creation blocks should be encapsulated in a transaction, so it either successfully finishes or fails

When I try to create new date or datetime type field, required is not checked -> date editor puts "invalid" value in the field default value and cannot be saved.

When item from relation is moved inside the view, currently it shows again the popup (as if it was inserted from the library) and the move fails

We will no longer need the:

1. Relation : areas_area_relation
2. Entity: areas_entities

to be created in the initial script.

The controller needs to be changed not to support these specific items

When switching from range to period , second value is not cleared.

1. month
2. any date

there should be only one value

We need to find a way how to make the lookup list process dynamic.
The case is the following:
I have 1:N relation item:item. A simple item can select a material item for its material_id field. If I use the general lookup field it will present all items in the system. We need only the material items to be presented

Is it possible to create a N:N relation that both the origin and the target fields are the record "id".

The case of creating an N:N relation between items -> products <> related products

There is a possible easy workaround of creating a specific unique guid field just to support this relation and thus not needing the "id" from both sides of the realtion, but still it will be nice to be able to make it in the "logical" way

The sidebar css needs to be fixed when the screen is narrow.

Currently the button is not hidden and allows the creation of an almost empty record

Sort option does is not implemented probably as it does not apply to the lists

On a list I am trying to filter the data with a checkbox value. I am using equals to -> true, but it fails to produce any results. Probably the string is not converted to boolean. Please check

When I try to post a new autonumber field, with the required checkbox - checked, the validation that I've got back from the API does not have the error record for the key 'defaultValue' as it has not been validated. Please check

In order to achieve better way to select and edit data from relation, we need to be able to set a couple of more properties to the view and list library items
Here are the new properties we will need:

1.fieldFromRelation

• fieldLabel
• fieldPlaceholder
• fieldHelpText
• fieldRequired
• fieldLookupList

2.viewFromRelation

• fieldLabel
• fieldPlaceholder
• fieldHelpText
• fieldRequired
• fieldLookupList
• fieldManageView

3.listFromRelation

• fieldLabel
• fieldPlaceholder
• fieldHelpText
• fieldRequired
• fieldLookupList
• fieldManageView

please remove the obsolete RecordsLimit property from the List model and related methods that use it.
The records limit should be hardcoded for all records to 1000

I think it will be better if we rename the "pluralLabel" property of the entity to "labelPlural" . Not having a double L will probably save some headaches

Please extend to support http://docs.mongodb.org/manual/reference/method/db.collection.distinct/
Thanks

The property field.format should be required when creating fields from these two types

We should include this data as well. The question is how many levels of inheritance of the views and lists we should include.

Trying to patch an entity recordView type and it is not applying the change.

When creating a query to match a fields value that has specific type - like guid or int,
the script does not match anything as it is treating the sumbitted value only as string.
case -> display only one record, by querying its Id field

On the text field creation screen:

1. fill name, label, default value
2. check required
3. check "all values of the field should be unique" default value is cleared and validation triggered

When i apply filter on list, view record and go back using back button on sidebar menu it redirects to list, but no to filter url.

I am trying to patch a record list type "type":"lookup". The api method returns success, but the change is not applied

The currency object should be extended with the following attributes:
"decimal_digits": 2,
"rounding": 0,
"code": "USD",
"name_plural": "US dollars"

There is a possible bug there. When I try to patch the list record with let's say new page size, it returns validation error with:
"errors":[{"key":"columns.relationName","value":null,"message":"Relation name is required!"},{"key":"columns.listName","value":null,"message":"List name is required!"}]

I try to patch only the view type with

{
type:"quickcreate"
}

but the response is an error from various missing names, eg. Relation name is required!.
This should not be happening when patching

When i leave from date empty, it sets current date when post the filter request.

I am trying to update a "is default" property of an existing record list. I get a number of validation error which also are very confusing:
"There is already an item with such list name or id!"
"Wrong name. There is no list with such name or id!"

Inside an active editor the right click should not trigger a save

We may remove the maskCharacter property and just always mask with a '*' star

Now the system requires at least one role to be assigned to each permission.
This is not good as I want to create an entity which does not allow its records to be deleted (like users)

would you give the "How-to use this code" section please.i downloaded the code, installed the mongodb but there were a lot of error about db so i am not able to run

I should not be able to submit as a column or as a field, the same list or view no matter if it is with relation or not.
Explanation:

1. I am managing "default_list" in an entity ABC
2. I have a relation XYZ ("N:N" type) in which both origin and target are the same entity ABC
3. I am trying to create a column in default_list, which is inserting the same list but via the relation XYZ.
4. I still received a blank JSON, due to circular list meta generation

We need to better handle the case when the date value is null. Now it appears "Invalid date". It should be just blank

The case of creating multiple N:N relations when both origin and target are the same entity with the same fields, should be supported from the interface.

Also when selecting N:N the "id" is not presented as an option for the target field

can you support sql server?

Uploading the readme images

Default value for ID field should not be manageable.

It says that accept underscore, but when I put it triggers validation error and when continue writing another character validation error hides.

When in the field meta there is defaultValue, minValue, maxValue, decimalPlaces, dates and etc,
the data is stored in the database as string, which is incorrect. It should be in the same data type as the expected field value. Example:
Percent field -> defaultValue,minValue and maxValue should be stored as decimal values are stored, not as strings

Pleace check whether the input and get method of working the percent data is the same.
In particular whether the input needs a value from 0 to 1, but when value gets returned by the API it is returned as from 0 to 100 value. Both should be from 0 to 1.

On create and update entity record, missing validation for required fields values.

EntityManager em = new EntityManager(service.StorageService);
TextField testField = new TextField();
var result = em.CreateField( entityId, testField );

The code snippet above try to create new field without any initialization and get system error result. My opinion is validation errors should be returned .

In order to be able to apply some rules of the input data we need two more properties for the entity field object:
-regexPattern
-regexFailedMessage

When in records view, there is a case when the requested recordView is missing (when dynamically generated in the list in most cases).
We need to properly handle the case with an error screen saying that the requested recordView was not found

In the same way we always include the record Id in the list data, please include it in the view data