Website Developer, business analyst
-
Support March 21st, 2020 @ 1:26 am
Hey Red, we are currently working on recoding the add on to support OAuth 2 and will notify/update the add on when that has been completed
Thank you for your time and patience
View Comment
-
Support March 10th, 2020 @ 8:51 am
The module has been marked as inactive until recoding for OAuth 2.0 has been completed
View Comment
-
Support March 10th, 2020 @ 8:48 am
OK, that's brilliant (sort of :=}) I couldn't for the life of me find anything on the Xero site that specified what was happening with NEW Private applications. Looks like I'll need to update the code. Once again, thanks for the feedback...
View Comment
-
Support March 9th, 2020 @ 11:39 pm
I have a number of customers who are using the plugin as is and have yet to get any queries back from them RE the implementation of OAuth 2.0 and their current installations NOT working. Because of this I have been assuming that the plugin is in fact still working. Have you tried installing it without success? If yes, I will set up a test bed and update the code as soon as I can.
Thanks for your feedback
View Comment
-
Support November 23rd, 2019 @ 1:27 am
Apologies, wrong link, it should be here:
https://suitecrm.com/suitecrm/forum/suitecrm-7-0-discussion/15731-add-custom-field-to-global-search
View Comment
-
Support November 23rd, 2019 @ 12:47 am
To enable the omni search functionality for the plugin you can follow the instructions in the following posting HOWEVER, it will only search the DEFAULT value as listed above. We will continue to see if there is a way to enable the full search over ALL values entered in the field
https://store.suitecrm.com/support/multi-entry-text-field/2387
View Comment
-
Support November 23rd, 2019 @ 12:16 am
Hey Ward, thanks for testing out the new field type and for your queries.
As an overview, the field is set to display in certain views (e.g. if you have used the field in the Accounts module and add it to the Accounts list view) ONLY the entry that is set as the DEFAULT selection when creating entries. That entry is also NOT hyperlinked to the underlying record. The values in the field are stored in the database using the following format
GTG Ltd^,^1^,^0^,^business^,^^|^Whatever Green Ltd^,^0^,^0^,^entity^,^The contents can be accessed via SQL queries. Obviously we acknowledge that this isn't optimal and are working on adding extra functionality. Each complete entry is seperated by the | symbol in a comma seperated set of values surrounded by caret ^ symbols. The first value is the name, the default value is the first entry after the name (1 = default) the second entry is the DNU entry (1 = DNU) the final entry is the value selected from the items drop down list
RE your specific questions (we are working on some of the functionality you have outlined):
Can all entries in this field be searched in the filter view search? Omni search?**
NO**, not ALL fields, as mentioned above ONLY the field that is set as default is searched via the filter view search. The functionality to enable full/Omni search has yet to be completedWill it show up as a field for the reporting module?
YES - on our tests, using the Accounts and Contacts modules as the basis of the report BOTH entities will display ALL values entered in the underlying module - please see the following image
Can we import into it and export from it?
NO/YES, currently this field is set to not import (NOT what the field type interface shows), An SQL import directly to the database field can be done, again, acknowledging that this is not optimal. We have tried a number of different methods per Suite documentation to turn OFF the importable setting when creating/installing the module, however none appear to be working. We are continuing to look for a solution.YES, you can export this field contents. It will be exported in the format outlined above and will use the values you entered when creating the fields list components field name as the delimiter
Is it visible to Studio for adding into sub-panels etc.?
YES however, as above, the subpanel will only list the entry that you have specified as the default - please note the following image and the AKA field. That field is pulling data from an extended text field in the Contacts module
We had considered adding a new type of display for the field when viewed in list view/subpanels etc however, after much thought we decided to only show the default listing. Our thoughts were that if we created a display field in perhaps a bulleted list, it could conceivably become quite cumbersome dependant on the number of values users created in their lists.
If you have any further questions, thoughts on how to make the field more 'usable', please don't hesitate to post them - once again, thanks for taking the time to test the field.
View Comment
-
Support September 5th, 2019 @ 9:30 pm
I've had a quick look at the Xero API and both the ability to add Tracking information and change the Status of a Xero group is available. For the Xero group status operation you may need to create a couple of extra fields in CRM, e.g. 2 drop downs, one listing the Groups in Xero (matching names OR Xero ID's) and one with the desired status you'd like the group set to. The Tracking option would probably require the same type of implementation...
Hope this helps
View Comment
-
Support September 5th, 2019 @ 9:20 pm
RE the information sent from CRM to Xero, some of the questions you've asked are answered in the documentation on this site, see the Docs section...
- Customer Information: As you know Xero is Account (Company) centric, NOT customer/contact centric. The module works in this manner. If you send an ACCOUNT from CRM to Xero it will create a new Account in Xero (OR link to an existing account that has the same name) ALL contacts in CRM that are related to that account will be attached as contacts. Alphabetical sorting will define which contact is the PRIMARY. If you send a CONTACT from CRM to Xero, it will check if the Contact belongs to an Account in CRM. If it does, the account from CRM is used to create the Account in Xero. ONLY the contact selected is added to that Xero account as the PRIMARY contact person. If the contact in CRM is NOT related to an Account, the Contact details from CRM are used to create the record in Xero, that contact is the Primary contact person
- This would be reliant on the Xero API. If the field that contains the tracking data in Xero is available, and the data is in CRM, it shouldn't be that big a customisation to the module
- As above for Xero grouping
For options 2 & 3 the ease of coding would not only be dependant on whether or not those fields are accessible via the Xero API but where in Xero the data is stored. If they are part of the account records in Xero, not that big a problem. If they are stored somewhere else, and accessible via the API, probably a bit more work would be required
I hope this answers your questions, I have also sent an email to Ivan Theron outlining some of these consideration.
Thank you for your time and patience
View Comment
-
Support September 5th, 2019 @ 9:07 pm
Hey AIE, the guides are all here, go to the Docs section and see the menu on the right of the page. There are videos and step by step walk throughs available
View Comment
-
Support September 4th, 2019 @ 11:31 am
Please have a look at our Installation Guide, FAQ or the readme.md file that is part of your installation zip file. The .pem and .cer files need to be uploaded to your installation: /custom/EntryPoints/XeroOAuth-PHP-master/certs directory
View Comment
-
Support September 3rd, 2019 @ 9:53 am
Sorry, the editor changed one line... the file is renamed to
original file name.BACKUP-time stamp
View Comment
-
Support September 3rd, 2019 @ 9:51 am
HI AIE.
You should have seen a notification screen after the installation of the module listing the files that had been located. A pre install script checks the following locations for the presence of the following files:
Accounts module
custom/modules/Accounts/metadata/detailviewdefs.php
custom/modules/Accounts/views/view.list.phpContacts module
custom/modules/Contacts/metadata/detailviewdefs.php
custom/modules/Contacts/views/view.list.phpInvoices module
custom/modules/AOS_Invoices/metadata/detailviewdefs.phpQuotes module
custom/modules/AOS_Quotes/metadata/detailviewdefs.phpGenerally, you should only have problems with the files in the metadata folder... If the files are located by the pre-install script (they exist in the folders specified) they are RENAMED to .BACKUP- This is so you can easily recover your previous views/setting by renaming the new files and renaming your old files.
If you open the NEW files in a text editor you will find sections within all of them that are surrounded by comments:
/************ custom xero button code, cut and paste as required *************/
You will need to cut and paste that section of code into your OLD files to ensure the functionality works. Unfortunately the module had to be created in this way as, at time of creation, there was no work around to add that custom code section to the detailviewdefs.php files. There was a workaround using Javascript, however that depended on a Suite theme being used that had a particular tag in it. I'm not sure if that has been addressed as yet. Once the detailviewdefs.php files have been updated any further changes you make to it using the Admin -> Studio interface should be fine.
If you'd like me to do the updates for you, please don't hesitate to email me your **OLD **files and the new ones and I'll get them updated ASAP
Thanks for your time and patience
View Comment
-
Support June 8th, 2019 @ 12:41 am
Updated code to allow unlimited download of invoices, Fixed code error
View Comment
-
Support June 8th, 2019 @ 12:40 am
Xero limited to 100 invoices per call. Functionality added to module for unlimited invoices
View Comment
-
-
-
Support June 8th, 2019 @ 12:36 am
Syncrhonise currency functionality added to the component
View Comment
-
Business Fundamentals has not rated any add-ons.
Business Fundamentals has not verified any add-ons.
Business Fundamentals has not created any Wanted Add-ons.