Disable Format doesnt Disable Format

[DanBrown]

Im using version 5.0, and when i create a new field in a custom module and set it as an "integer" with "Disable Format" checked, i can still format it and enter my own number. I would like the field to assign its own number so every case has a unique number automatically, Am i missing something?

Thanks.

[eNick]

No you need to set it to auto increment.

See Mike Solomon's answer (near the bottom) in this thread...

http://www.sugarcrm.com/forums/showt...auto+increment

Alternately, just change the MySql column definition to Autoincrement.

[DanBrown]

Thanks for the reply.
As default the column is set to auto_increment, the problem seems to occur when i make a change to the fields layout and re deploy the module. Even after this the column is still set to auto_increment in the database, but a number can now be manually inputted into the number field.

Thanks

[eNick]

To stop a number being manually input, use 'type'=>'readonly' in the editview.def.

This is similar to the Case Number on Cases which is autogenerated and read only....

array('name'=>'case_number', 'type'=>'readonly', 'displayParams'=>array('required'=>true))

And yes, unfortunately, direct changes to the viewdefs are typically lost if you make further changes in studio/module builder.

[DanBrown]

Thanks for the reply.
Am i right in saying the best thing to do is configure the modules fully before deploying them and then leave them? Where can i locate this editview.def to change to read only.

Thanks again

[eNick]

All I can say is that our approach is that when we are altering a file which is potentially going to be overwritten through either the studio or through a system upgrade (ie. if we're changing core code), we place a file in the same directory documenting the changes and usually set the file permissions to read only.


So, if we hand edit an editviewdef.php we'll set it's permissions to read only and create a file called editviewdef.php.readme and document in there any changes we made. That way it can only be overwritten if someone changes the permissions and then they will (hopefully) read the documentation and re-apply the changes.

And yes, we tend to make sure it's all correct before deploying - so our process is to do all the changes we can through the studio/module builder etc. and then once we're happy with those, to add in any changes which require hand edits and then deploy again.

[DanBrown]

Thanks for your help ill give it a go.

[clint]

The "disable format" option on a custom integer field removes the thousands separator for the display in the Detail View and List Views.

[DanBrown]

I am still getting an issue where i cannot 'blank out' the unique number field. It is crucial that this area is automatically assigning issue numbers as users will assign which ever number they like. Iv tried looking for specific editviewdef.php files and cannot.

Please bear in mind im new to sugar and php so i dont understand much of your code...

Many Thanks

[eNick]

Ok, so to summarise where we are:


Disable format has nothing to do with your problem. It's purpose is to stop Sugar formatting your number. So if you enter 123456 disabling the formatting prevents it being displayed as 123,456 (with a comma).

So, that leaves two issues:

1) Making it autoincrement, which it sounds like you've done.
2) Making the field read only so people can't change it.

To make a field read only you need to make a change in the editviewdefs file.

That will be located in...

custom/modules/<your module name>/metadata/editviewdefs.php

Inside this file you'll see an entry similar to this...

array('name'=>'<your field name>', 'type'=>'<something - probably integer>', 'displayParams'=>array('required'=>true))

And you need to change type to 'readonly'

That will (or should!) prevent it being editable. You'll probably need to do a Repair to rebuild the cached file after the change. And if you deploy your package again it may get overwritten.