Rukovoditel Support Forum

On the other hand I do not understand what you mean by "apply accessibility in operational entities, making the Company as the connector only with Record Visibility" It's exactly like Sergey's example in the docs. I added more fields to entity Users including company, position, etc. Some ...

Hi, sorry to barge in but I had faced similar situation as yours, only I decided to apply accessibility in operational entities, making the Company as the connector only with Record Visibility. Anyway if you want to automate filling that field, maybe you can create a PHP Code field as post-input pro...

Yes, but the Auto-increment field cannot be reset yearly or with the condition that I wanted. You're right. I just checked the class, it search the min/max of entire table, not last-record field value. Only when the entity has parent will enable it to separate numbering. What I'm still lack is the ...

I dont think it's possible. The year is dynamic to use as prefix. But you can combine with PHP Code and you use this field for numbering. For example: if(!strlen($current_field_value)){ //Let's say the entity id is 10, increment number field id is 200, and the date_added is the year reference, and y...

The field [997] and [775] are both fieldtype date and, if you can see the entity table via phpmyadmin, their data type is integer (or bigint to be exact) and value [774] is not dynamic, right? Try testing the query directly in phpmyadmin to the blank field_997 record: SELECT IF(field_997>field_775,f...

The problem predictably occured because when the field value is not empty, you requery the entity instead and in editing, it will result empty value once again. I think you'd better lock the value like this: if(!strlen($current_field_value)) { $date = [date_added]; $year = date('Y',$date); //the dat...

I see. So you're making increment number that reset each year. I think you can make your code simpler so that you just access mysql once instead of 3 times, for example: $date = [date_added]; $year = date('Y',$date); $query = db_query("SELECT COUNT(*) c FROM app_entity_101 WHERE date_added < &q...

That's strange.
In my 2.9.2, I can assure you that if a user has only access View, when he's assigned a role which overrides his privilege in parent entity, he'll get that access for specific subentity (create, update, delete, etc).

Well, I suggest that because I see your query is dynamic, finding for duplicates. I guess that's not the whole code, right? Because I cant see where $output_value gets its initial value. When you get any duplicate eventually, then at least one previous record will get the wrong value and you have to...

Yep, that's right!