Quickbooks Online Estimate Object Missing One Custom Field

  • 114Views
  • Last Post 1 weeks ago
0
votes
Sohrab Niramwalla posted this 29 March 2022

Hi,

We use the QBO connector in a package to fetch all items in the QBO Estimate table.  Our QBO Estimates have three custom fields:

P.O. Number, Sales Rep, Y/N

The third field, Y/N does not appear in the list of fields in the Skyvia listing.  Using the Power BI Quickbooks.Tables() connector allows us to see and fetch the values in the Estimates table.

What can we do on the Skyvia side to make this column's data available?  I note that one of your documents states that QBO custom fields that have quotation marks in the name are not available, but this field does not have quotation marks.

I have attached screenshots with some relevant information.

EDIT: after renaming the custom field in QBO to remove the / character, in case that was the cause, we are still unable to see the field in the Estimates table.  Note that using the QBO API explorerer (https://developer.intuit.com/app/developer/qbo/docs/api/accounting/all-entities/estimate), the field IS visible as expected, see the second screenshot added just now.  

Thanks,

Sohrab

Attached Files

Order By: Standard | Newest | Votes
0
votes
Mariia Zaharova posted this 31 March 2022

Hello Sohrab,

 

Thank you for contacting us.

 

Please try these steps and let us know the results:

1) Disable Metadata Cache in your QuickBooks connection.

2) Try creating a new QuickBooks connection.

 

If this does not help, please send us settings for this custom field in QuickBooks so that we can try to reproduce it on our side.

 

Looking forward to your reply.

 

Best regards,

Mariia

0
votes
Sohrab Niramwalla posted this 31 March 2022

Hi Mariia,

Thanks for your reply.  We created a new QBO connection with Metadata Cache disabled, and via Builder, are still unable to see the expected custom field on the Estimate table.  I have attached an annotated screenshot showing an Invoice, the custom field configuration and the results of the Builder field list from Skyvia.  Note that in my previous screenshot, we *DO* see the field returned when we use the QBO API explorer accessing the estimate entity.

Thanks for your help,

SohrabQBO Custom Field Config etc

0
votes
Mariia Zaharova posted this 04 April 2022

Hello Sohrab,

 

Thank you for the details.

 

We will investigate the issue more clearly and contact you as soon as any news is available.

 

Best regards,

Mariia

0
votes
Sohrab Niramwalla posted this 06 April 2022

Hi Mariia,

Can you please provide an update?  We need to know if Skyvia will be able to allow us to get the custom field data from QBO, or if we will have to find a different service in order to get this data.

Thanks,

Sohrab

0
votes
Mariia Zaharova posted this 08 April 2022

Hello Sohrab,

 

 

Sorry for the delay.

 

Unfortunately, we still cannot reproduce the same issue on our side.

We assume, the issue may be related to the limitation mentioned here: https://developer.intuit.com/app/developer/qbo/docs/workflows/create-custom-fields

https://developer.intuit.com/app/developer/qbo/docs/workflows/create-custom-fields#advanced-custom-fields

With QuickBooks Online Advanced, customers can create up to ten custom fields with various data types; 
however only the first three String custom fields will be available through the existing API functions outlined here.

 

We will continue investigating possible reasons for this issue, however, we would also recommend you to contact QuickBooks Support. 

 

Best regards,

Mariia

0
votes
Sohrab Niramwalla posted this 12 April 2022

HI Mariia,

Thanks for your update. Can you please confirm that you use the QBO API to get the data? If so, note that we *CAN* see the data in question when we use their API in their developer environment.  Note that the field in question IS one of the "first three String custome fields" in QBO.  Could the issue be with the "/" character in the Y/N field name that prevents Skyvia from successfully retrieving the information?  Have you tested that setup out by putting a "/" in your test custom field in your QBO and then trying to fetch the data? I know that you have a note about not being able to use a quote character.  From the QBO support side, because the data is visible via the API, they are pointing the investigation back to Skyvia.

0
votes
Mariia Zaharova posted this 18 April 2022

Dear Sohrab,

 

Sorry for the delayed response.

 

Yes, Skyvia works with QuickBooks via API. We still could not reproduce the issue on our side. We can see custom fields with the "/" in their name. Please check the link.

 

We will continue checking possible issues and contact you as soon as possible.

 

Meanwhile, can you please send us a screenshot of these custom fields settings from QuickBooks (Settings -> Account and Settings -> Sales)?

 

Best regards,

Mariia

0
votes
Sohrab Niramwalla posted this 18 April 2022

Hi Mariia,

Thanks for your continued support.  Please see the screenshots as requested:

Please note that we have nine active and two inactive custom fields.  I have shown both in case that helps.

Sohrab

0
votes
Mariia Zaharova posted this 20 April 2022

Dear Sohrab,

 

Thank you for your reply.

 

We will answer you as soon as we have any news.

 

Best regards,

Mariia

0
votes
Mariia Zaharova posted this 4 weeks ago

Dear Sohrab,

 

We are sorry for the delay with this issue. We still could not reproduce the issue on our side, however, our developers are investigating it.

Meanwhile, could you please check whether this field is available if you access your QuickBooks instance via Postman

 

Looking forward to your reply.

 

bets regards,

Mariia

0
votes
Sohrab Niramwalla posted this 4 weeks ago

Hi Mariia,

If you can please include some detailed steps on how to connect to QBO and retrieve the fields on an estimate record with Postman, we will try and let you know what we find.

Thanks,
Sohrab

0
votes
Mariia Zaharova posted this 4 weeks ago

Hello Sohrab,

 

Please follow this article https://developer.intuit.com/app/developer/qbo/docs/develop/sandboxes/postman and use the same requests as you tried in your QuickBooks API tests (screenshots above).

NOTE: at Step 3, add the first collection: For QuickBooks Online Accounting API: Get a collection of individual resource endpoints. This collection includes requests for the Estimate object.

 

If you encounter any difficulties with this, please let us know and we will give you more detailed steps here.

 

Best regards,

Mariia

 

0
votes
Sohrab Niramwalla posted this 3 weeks ago

Hi Mariia,

We have completed the steps. Please note in the screenshot that the Custom Field on the Estimate with Name "Y/N" is visible, as expected.

When can we expect a resolution?

Sohrab

0
votes
Mariia Zaharova posted this 3 weeks ago

Hi Sohrab,

 

Thank you for the details.

The development team is working on this case at the moment. I will inform you about the results in a few days.

 

Thank you for your patience with this.

 

Best regards,

Mariia

0
votes
Mariia Zaharova posted this 3 weeks ago

Hi Sohrab,

 

We have investigated the issue once again and can confirm the issue is not related to Skyvia. We suppose the issue is still connected to the QuickBooks API limitation in regards to the visibility of the 3 custom fields (even if you have configured 10 ones) because according to QuickBooks support forums, this limitation is still actual for many of their users.

We have performed several tests with QuickBooks Advanced and created7 fields - some of them are available via API and some of them are not (checked via Skyvia, Postman, etc.). We cannot confirm how QuickBooks API determines which fields are visible and which ones are not on the steps of retrieving metadata.

We recommend you to:

1) Try to create a new QuickBooks connection once again (set Metadata Cache to Infinite).

2) Pay attention to the fact that the "Y/N" field in your QuickBooks instance is marked as "Not printed on form". Probably, this is the reason why this field is not available in Skyvia.

 

If these 2 steps do not help, we recommend contacting QuickBooks support.

If we have ane other comments or suggestions, we will definitely post them here.

 

Best regards,

Mariia

0
votes
Sohrab Niramwalla posted this 2 weeks ago

Hi Mariia,

I emailed this response to Darina via email, but wanted to share with you as well:

However, though I’m by no means an expert, nor do I know how Skyvia works, it seems to me that after we conducted the tests requested using Postman to connect to our QBO, and that test returned the field that Skyvia is NOT returning, and since Postman is a “neutral third party”, the reasonable conclusion is that the source of the issue lies somewhere on Skyvia’s side, and not on the QBO side.

Were we to pursue opening tickets with QBO, I’m certain they would ask us to verify the field’s visibility using something like Postman, and since Postman returns the field without problem, QBO would suggest that the cause was somewhere OUTSIDE of QBO.

Is that an incorrect conclusion? How could it be that if Postman CAN see the field, that the problem is on the QBO side?

Thanks,

Sohrab

0
votes
Mariia Zaharova posted this 1 weeks ago

Hello Sohrab,

Thank you for your reply. I completely agree with your comments and would say the same things. However, after investigating the issue by our developers, we cannot find the issue on our side. We performed many tests with different combinations and concluded the issue is related to the limitation of QuickBooks API regarding the visibility of only 3 custom fields (even if you have more than 3).

We will definitely continue working on this issue in order to get more explanations regarding this, however, currently, we can advise you to try the steps we proposed in our previous reply and/or contact QuickBooks support.

 

Best regards,

Mariia

Close