Join The Community Sign Up For Club Zenatta

Article Read Time:

2 Min

Search
Search

Subcribe To Our Channels:

Train Your Entire Team
With Our Zoho Team Training:

Check Out Our
Zoho Marketplace Extensions:

Join Our FREE
Zoho Community:

AZAAZ – Volume 1, Issue No. 24

Questions Answered

💬 1. (0:42) We have a customer who dropped off a serialized item that they own that we are performing repairs on. We then sent it to our technician at another location to perform the repair. I need to be able to track that the customer dropped the item off to me, I received the item, transferred it to our technician and repairs are being done, and then collect payment when the repairs are finished, and track that the item was returned to the customer. Since it’s not our Inventory, I don’t think adding it as an item and performing transfer orders in Zoho Inventory would be the correct approach to track its movement. Any ideas for how to handle the scenario?

💬 2. (3:39) We currently have two [Zoho Mail Basic] accounts and would like to upgrade it to 50 GB. However, we are having trouble understanding how to do it. Could you please help me?

💬 3. (5:54) How do you set availability for a meeting with a CRM User or CRM Group so the full day isn’t open for bookings, but just the hours you want to open?

SMS For Zoho CRM by MessageMedia ad banner with 50% off the first three months special

💬 4. (8:15) What is the best community to learn and share experiences about Zoho One? 

💬 5. (10:57) We are currently on Creator v5 and have the option to upgrade to v6.  One of the main goals with Creator is to create a customer portal for our agencies.  It seems as though everywhere I read, people are pointing to ZPortals however we would like to grasp the full capacity of Creator prior to going down that route. Do you know the difference between the v5 and v6 and would you recommend staying with 5 or upgrading to 6?

💬 6. (15:58) Hi I’ve been using Zoho Books API for the last 7 years. I’ve never run into any throttling or limits per minute. Then July 2nd we were hit with throttles. Zoho told me that the limit was 100 per minute. So, I adjusted any code that was making API calls so it would be well below the 100 per minute. Then I hit another throttle at the end of July and they notified me that the limit was now 30 calls per minute. Is anyone else experiencing this? Seems to me that now the API is only useful for API calls such as creating a record. You can’t query the API for anything more than a record or two. Additionally if you have a scheduled function running in CRM or Books it’s not going to be able to do much with those limits and schedules only running every 30 minutes. Seems to me the next best option would be to have cron jobs running on a separate platform such as Google Cloud, Zoho Catalyst, etc if you need to do any large querying/retrieving or mass updating of data via the API

💬 7. (29:45) Linkmatch sounds like a great tool, but I’m wondering if there are any security concerns with it being a tool outside of the Zoho universe. I’m also wondering if there are any issues with violations of LinkedIn’s policy. 

Question 4: Club Zenatta – https://club.zenatta.com & Zoho Community – https://community.zoho.com/

Billy Bates

Senior Web Developer

Billy is a Wordpress Developer with an eye for design. His knowledge will help our company website and client sites meet their goals. Billy and his young family have just moved to Ashland Oregon, and are looking forward to exploring the area’s amazing beer, wine, and food. He also has a passion for synthesizers and drum machines.

Lucas Sant'Anna

Consultant

With a background in Operations Research and Data Analysis, Lucas is a Brazilian programmer that likes to get stuff done quickly and reliably. In previous jobs, he implemented industrial job scheduling, fleet management and detailed long-haul route optimization – among other data-driven processes – to reach objectives of increased profit and reduced wasted resources. His goal is to make Zoho fully automated and with more meaningful data for spot-on decisions.

.

.