Errors related to "MasterTaskInfo" and "VariationMasterTask" when saving purchase document in V10 via API

Good evening

A direct integration into the purchases should work without problems. I tested the example below with the latest release available and it worked fine.

This code is called direct to motor or calls a specific component.

using ErpBS100;
using CmpBE100;
using StdBE100;
using System;
using static StdBE100.StdBETipos;

namespace Invoice.V10.Sample
{
    class Invoice
    {
        static void Main(string[] args)
        {
            CreateInvoice();
            Console.ReadKey();
        }

        static void CreateInvoice()
        {
            StdBETransaccao objStdTransac = new StdBETransaccao();
            ErpBS bso = new ErpBS();
            string strAvisos = string.Empty;
            bool blnModoPrimario = true;

            Console.ForegroundColor = ConsoleColor.White;
            Console.Write("Open API.... \n");

            bso.AbreEmpresaTrabalho(EnumTipoPlataforma.tpEmpresarial, "Demo10", "", "", objStdTransac, "Default", blnModoPrimario);

            if (bso != null)
            {
                CmpBEDocumentoCompra invoice = new CmpBEDocumentoCompra();

                Console.Write("TipoDoc: ");
                var tipoDoc = Console.ReadLine();
                invoice.Tipodoc =tipoDoc;

                Console.Write("Entidade: ");
                var entidade = Console.ReadLine();
                invoice.Entidade = entidade;

                Console.Write("Serie: ");
                var serie = Console.ReadLine();
                invoice.Serie=serie;

                Console.Write("Artigo: ");
                var artigo = Console.ReadLine();

                invoice.TipoEntidade = "F";

                Random rnd = new Random();
                invoice.NumDocExterno = rnd.Next(1000).ToString();

                try
                {
                    Console.Write("A gravar o documento...\n");
                    bso.Compras.Documentos.PreencheDadosRelacionados(invoice);
                    bso.Compras.Documentos.AdicionaLinha(invoice, artigo);
                    bso.Compras.Documentos.Actualiza(invoice, ref strAvisos);

                    if (strAvisos.Length > 0)
                    {
                        Console.ForegroundColor = ConsoleColor.Red;
                        Console.Write($"Error writing document. \n { strAvisos};");
                    }
                    else
                    {
                        Console.ForegroundColor = ConsoleColor.Green;
                        Console.Write("Document saved with success. \n");
                    }

                }
                catch (Exception ex)
                {
                    Console.ForegroundColor = ConsoleColor.Red;
                    Console.Write($"Unable to save document. \n {ex.Message};");
                }
                finally
                {
                    Console.ResetColor();
                    bso.FechaEmpresaTrabalho();
                }
            }
        }
}

The project where this code example was running is a new class library, in the context of a solution that includes our base classes integrating our system with ERP, but which was invoked by a test application console already with several years, that had changed to the target framework 4.7.1.

After confirming that the example provided by Sergio worked on a new project, I added a new console application in the same solution, and added the same references to the previous one, and both the example of Sergio Sereno and mine already passed to work. So I tested integrate a receipt of a vendor database made on a PDA in V10, and it already worked as expected.

I suspect that the origin of the problem in the original application console might be related to having changed the target framework, but not having updated the previously added references, notably the Entity Framework.

This gives the information to others who may be migrating "in place" previous Spring integration projects.