Config. Package Errors

(0) Share

Report

Posted on by jaybeegee

135

Hi!

We created a config package to faciltate the creation of PO lines which sometimes run in the 100s of item lines.

We then created the PO and set the PO Name and Vendor Name in the PO Header which we used in the XL template. Finally we tried to to upload the PO lines via the configuration package but with no joy.

It seems that the type ITEM is not being set and if we change the type to G/L Entry we get the same error. Pretty sure that the products we are testing with exist.

Any ideas what we can check for?

thanks in advance

All responses (13)

Answers (1)

Suggested answer

MahGah 15,428 on at

Like (0)

Report

RE: Config. Package Errors

Thanks for info. I see that you have on-prem version but installed on Azure (Saas). I do not have much information about that. Please create new question and ask community and I am sure you can find an answer.

I saw below guideline but I am not sure if this method even works

https://www.1clickfactory.com/blog/setting-up-the-excel-add-in-for-editing-business-central-data-using-powershell/

Thanks
jaybeegee 135 on at

Like (0)

Report

RE: Config. Package Errors

No we do not seem to have that option!

You mention you are on BC19 we are actually on a different version (blush)

Pure SaaS version was not available in our region until recently.
Suggested answer

MahGah 15,428 on at

Like (0)

Report

RE: Config. Package Errors

That is strange

We are in SaaS and BC 19 and we have this. Do you see that icon in your page? I am in Purchase Order List
jaybeegee 135 on at

Like (0)

Report

RE: Config. Package Errors

thank you.

we are on the saas version.

I have followed the steps and left the company blank which I understand will extend across all companies but no luck.

I have tried logging in and out.

I noticed we have this too:

No sign of the PAGE option - what are we missing?
Suggested answer

MahGah 15,428 on at

Like (0)

Report

RE: Config. Package Errors

Are you on SaaS or on-prem?

For SaaS it is super simple just requires user permission: https://cargas.com/blog/enable-or-disable-edit-in-excel-in-microsoft-dynamics-365-business-central/

For on-prem more step requires https://www.encorebusiness.com/blog/how-to-set-up-edit-in-excel-for-dynamics-365-business-central-saas/

Thanks
jaybeegee 135 on at

Like (0)

Report

RE: Config. Package Errors

Yes I agree 100%!

We are struggling to get it installed - I have seen the ms docs but we did not manage!
Suggested answer

MahGah 15,428 on at

Like (0)

Report

RE: Config. Package Errors

Great.

I still think Edit in Excel is the better way to go. It is more accurate and easier for user. In addition, if this is a daily case in this company maybe developing XML Importer for PO can help.

If my answered help you please verify it to help others.
Suggested answer

jaybeegee 135 on at

Like (0)

Report

RE: Config. Package Errors

Yes I followed your steps and it worked.

Previously I would do validate and the errors would come up! If I do apply without the validate option it works.
Suggested answer

MahGah 15,428 on at

Like (0)

Report

RE: Config. Package Errors

Hi

Can you please compare your method with this guideline and see if they are similar and if you still receive the same error.

1) Create PO in BC

2) Add one line to it.

3) Go to configuration package and only select table 39. You do not need table 38

4) Make sure only include the fields I marked below and make sure Valid is on.

5) Then go to Table -> Filter and then select Field ID 3 and then for filter enter the PO number that you just created.

6) Download the Excel file.

7) Make sure to complete all included fields. Vendor should be the vendor that you added in PO. Please increase Line No by 10,000. (later you can try this without line no as well).

8) save and upload and apply the file.

Thanks
jaybeegee 135 on at

Like (0)

Report

RE: Config. Package Errors

thank you for your prompt and exhaustive response.

When we created the configuration file and added the two tables 38-PO Header and 39-PO Details we did not modify the fields to include and left them all in.

It must be something else.