bcaverly - Profile

Documentation July 20th, 2016 @ 10:20 pm

Looks great - but, does this reporting tool properly implement/respect "team" (row level) permissions as implemented in SugarCRM Pro? If not it is unusable for us. Thanks!

View Comment

Setting the upload field to required still asks for a file in EditView when you edit the record after it has been saved with an uploaded file

Support March 10th, 2016 @ 8:51 pm

Jason - sending you a package that will replicate this problem. :)

View Comment

Setting the upload field to required still asks for a file in EditView when you edit the record after it has been saved with an uploaded file

Support February 19th, 2016 @ 6:13 pm

HI Jason, Sorry for the delayed reply - I missed this question...

To get the QuickCreate form to work you must just have a quickcreatedefs.php file in the /modules//metadata folder. We access that by having the Edit button widget enabled in the subpanel definition - by default /modules//metadata/subpanels/default.php That usually looks like:

    &#039;edit_button&#039; => 
    array (
      &#039;vname&#039; => &#039;LBL_EDIT_BUTTON&#039;,
      &#039;widget_class&#039; => &#039;SubPanelEditButton&#039;,
      &#039;module&#039; => &#039;sapr_bylaws&#039;,
      &#039;width&#039; => &#039;4%&#039;,
      &#039;default&#039; => true,
    ),

Clicking the edit button then "edits" the record in the Quick Create form. If there is no quickcreatedefs.php then it edits the record using the full form.

I hope you can find an answer to this because it is a real headache for me right now! :( Feel free to email me directly if I can help further.

Thanks, Bob

View Comment

Setting the upload field to required still asks for a file in EditView when you edit the record after it has been saved with an uploaded file

Support February 5th, 2016 @ 6:05 pm

So it seems I spoke to soon with this "fix"! :(

Implementing this gets rid of the problem with an already set field being "required" - but now I can't get the form to pop up in Quickcreate - it forces it to go to the full form! :(

Anyone else got any ideas? This is becoming a real showstopper for me.

Bob

View Comment

Setting the upload field to required still asks for a file in EditView when you edit the record after it has been saved with an uploaded file

Support January 26th, 2016 @ 9:57 pm

hmmm - editor format functions don't appear to work quite right. :( Those paths should be: /custom/modules/[modname]/views/view.edit.php and /modules/[modname]/metadata respectively.

View Comment

Setting the upload field to required still asks for a file in EditView when you edit the record after it has been saved with an uploaded file

Support January 26th, 2016 @ 9:54 pm

Hi Jason,

Yes I'm on the latest version.

I have found a workaround. This seems to be a SugarCRM issue that it does not implement validations exactly the same in the Quick Create form as in the edit view. To get around this I did the following: in /custom/modules//views/view.edit.php - add the following code in the constructor:

class _**<modname>**_ViewEdit extends ViewEdit {

    public function __construct()
    {
        parent::ViewEdit();

        //use this file for sub-panel as well as for editview
        $this->useForSubpanel = true;
        $this->useModuleQuickCreateTemplate = true;
    }
...

then in /modules//metadata - remove (or rename) the file quickcreatedefs.php

This will then force SugarCRM to actually use the edit view definition for the quick create view.

This may not be a viable solution for all users - but it is working for me so far.

Thanks, Bob

View Comment

Setting the upload field to required still asks for a file in EditView when you edit the record after it has been saved with an uploaded file

Support January 26th, 2016 @ 9:27 pm

Hi Jason,

I am seeing this same issue when using the FileUpload field on the Quickcreate form. Everything works fine when editing/saving the module in the "Full Form", but if I edit in the Quickcreate and a file is already saved - clicking the Save button reports a "Missing required field". This is a bit of a show stopper for me at the moment because we don't want the end user using the full form for this module if we can avoid it.

Thanks, Bob

View Comment

"Not a deployed module" error

Support December 18th, 2015 @ 7:36 pm

FWIW, the problem appears to be in: \modules\ModuleBuilder\parsers\views\DeployedMetaDataImplementation.php The error occurs at line 44 because the passed in module name does NOT include the "{key}_" prefix.

Hope that helps. Bob

View Comment

"Not a deployed module" error

Support December 18th, 2015 @ 3:55 pm

Hi, thanks for the quick response! I am looking to use the FileUpload field in several places in a fairly large custom package that will include several related modules. I would REALLY prefer to be able to include these fields as 'core' fields in my packages rather than have to work in both Module Builder and then create additional 'custom' fields via Studio. In fact there will be some fairly extensive hand coding needed for things like logic hooks, etc. that can't be properly handled in Studio any way so I'm trying to avoid using studio at all for this sub-project.

Is it possible make this field type work in Module Builder - or alternatively, can you provide instructions for manually adding this filed type so I will not need the _cstm table, etc.

Thanks, Bob

View Comment

ADD-ONS

SOLUTIONS

RESOURCES

ABOUT