by Captivea - SugarCRM Advanced Partner

Enter a French Company's Siret / SIREN number and get valuable information from the most well known company data websites such as societe.com or manageo.fr in one click right from Sugar. Learn when the business was created, how many employees they have, activity code, and even get insight to their financials.

Includes a 30 day guarantee
Try it Now

By clicking you consent to be contacted by the developer

#3507 - Bug when opening a record

Open Bug? created by enes.saridogan 4 years ago

Hi,

After implementing the custom field in the Account (of any other) module, I get an error message once the page finished loading:

erreur siret.PNG

I also found the part of code that is buggy, the file Siret.js , line 34. When the page loads for the first time, the variable "value" is undefined, and on line 34 we are trying to call the function replace on an undefined value.

Can you confirm you have the same behaviour, and by the way provide a patch ? Many thanks,

Enes

  1. enes.saridogan member avatar

    enes.saridogan

    4 years ago

    No news ?

  2. enes.saridogan member avatar

    enes.saridogan

    4 years ago

    Any news ? The issue is still blocking ...

  3. Captivea member avatar

    SugarCRM version ? flavor ? onsite or on demand ? PHP version used ?

    we are not aware of any problem regarding loading the field so maybe do you have an incompatibility regarding maybe other modules or development made on your instance ? did you try on a fresh one ?

    The message you get let me think about a problem in licence validation

    Regards

  4. enes.saridogan member avatar

    enes.saridogan

    4 years ago

    Here are the informations:

    SugarCRM version: 7.9.0.0 and 7.9.2.0 Flavor: Enterprise PHP version: 5.6.32 Installation: On site

    The licence is valid, there is no problem on this side.

    The problem is in the Siret.js file, located in custom/clients/base/fields/Siret. In the render function, the variable value is undefined at the first call, that's why the problem appears. You can fix it by adding this code after the following line:

    var value = this.model.get(this.def.name); if (value === undefined) { return; }

    It's a pity because I still get this issue, and after the fix I provide everything is ok.

  5. enes.saridogan member avatar

    enes.saridogan

    4 years ago

    Is it possible to have a quick reply without leaving a new message ? Many thanks,

    Enes

  6. enes.saridogan member avatar

    enes.saridogan

    4 years ago

    Can you help us please ?

This case is public. Please leave out any sensitive information such as URLs, passwords, etc.
Saving Comment Saving Comment...