@josecgomez
We created a dll and have imported it into epicor. Now, running this code we get a message that says we can’t mark buy-to-order and make direct. Any suggestions? We do not want it make direct.
using (var so = Ice.Assemblies.ServiceRenderer.GetService<Erp.Contracts.SalesOrderSvcContract>(Db))
{
var dp = so.GetByID(orderNum); //variable 'ds' is changed to 'dp' since 'ds' is already used as a parameter
for (int i = 0; i < dp.OrderRel.Count; i++)
{
if (dp.OrderRel[i].OrderLine == quoteDtl.OrderLine)
{
dp.OrderRel[i].RowMod = "U";
so.ChangeOrderRelBuyToOrder(true, ref dp);
so.Update(ref dp);
}
}
}
using (var so = Ice.Assemblies.ServiceRenderer.GetService<Erp.Contracts.SalesOrderSvcContract>(Db))
{
var dp = so.GetByID(orderNum); //variable 'ds' is changed to 'dp' since 'ds' is already used as a parameter
for (int i = 0; i < dp.OrderRel.Count; i++)
{
if (dp.OrderRel[i].OrderLine == quoteDtl.OrderLine)
{
dp.OrderRel[i].RowMod = "U";
}
}
so.ChangeMake(false, ref dp);
so.ChangeOrderRelBuyToOrder(true, ref dp);
so.Update(ref dp);
}
This is the error we are getting.
Description: BPM runtime caught an unexpected exception of ‘EntityException’ type.
See more info in the Inner Exception section of Exception Details.
Inner Exception: The partner transaction manager has disabled its support for remote/network transactions. (Exception from HRESULT: 0x8004D025)
The partner transaction manager has disabled its support for remote/network transactions. (Exception from HRESULT: 0x8004D025)
Even if we comment out change make and changeorderrelbuytoorder we still get the error. Something else is missing.
using (var txScope = IceContext.CreateDefaultTransactionScope())
{
using (var so = Ice.Assemblies.ServiceRenderer.GetService<Erp.Contracts.SalesOrderSvcContract>(Db))
{
var dp = so.GetByID(orderNum); //variable 'ds' is changed to 'dp' since 'ds' is already used as a parameter
for (int i = 0; i < dp.OrderRel.Count; i++)
{
if (dp.OrderRel[i].OrderLine == quoteDtl.OrderLine)
{
dp.OrderRel[i].RowMod = "U";
}
}
so.ChangeMake(false, ref dp);
so.ChangeOrderRelBuyToOrder(true, ref dp);
so.Update(ref dp);
}
}
that allowed the code to run without errors however it doesn’t change the make direct nor buy to order. Make direct is still selected and buy to order is still unchecked.
We have it running on post processing on Quote.CreateOrder.
There is at least one compilation error.
Update.CommonTypes.cs(472,33): error CS0433: The type 'JobProdTable' exists in both 'Erp.Contracts.BO.JobEntry, Version=10.1.600.0, Culture=neutral, PublicKeyToken=5d3fa3c7105d7992' and 'Erp.Contracts.BO.SalesOrder, Version=10.1.600.0, Culture=neutral, PublicKeyToken=5d3fa3c7105d7992'
Update.CommonTypes.cs(313,55): error CS0433: The type 'JobProdRow' exists in both 'Erp.Contracts.BO.JobEntry, Version=10.1.600.0, Culture=neutral, PublicKeyToken=5d3fa3c7105d7992' and 'Erp.Contracts.BO.SalesOrder, Version=10.1.600.0, Culture=neutral, PublicKeyToken=5d3fa3c7105d7992'
Does anyone have any idea on how to get past this issue?
We’ve run into the same sort of issue, although with SalesOrder and RMAProc. We’re in 10.1.400.28.
You indicated that the .Dll dataset conflict was resolved for 10.1.600; is this just for the SalesOrder / Quote dataset conflict, or were other dataset conflicts resolved as well ?
Old thread but getting same error using SO BO from JobEntry update. We are on version 10.2.700.
Is it me or the bug still there? Thanks
There is at least one compilation error.
Update.CommonTypes.cs(492,33): error CS0433: The type ‘JobProdTable’ exists in both ‘Erp.Contracts.BO.JobEntry, Version=10.2.700.0, Culture=neutral, PublicKeyToken=5d3fa3c7105d7992’ and ‘Erp.Contracts.BO.SalesOrder, Version=10.2.700.0, Culture=neutral, PublicKeyToken=5d3fa3c7105d7992’
Update.CommonTypes.cs(328,55): error CS0433: The type ‘JobProdRow’ exists in both ‘Erp.Contracts.BO.JobEntry, Version=10.2.700.0, Culture=neutral, PublicKeyToken=5d3fa3c7105d7992’ and ‘Erp.Contracts.BO.SalesOrder, Version=10.2.700.0, Culture=neutral, PublicKeyToken=5d3fa3c7105d7992’
I’m getting the issue with ‘exists in both’ and when trying to add a Method Directive to Labor.Update().
The exact error is:
The type ‘LaborDtlTable’ exists in both ‘Erp.Contracts.BO.Labor, Version=10.2.600.0, Culture=neutral, PublicKeyToken=5d3fa3c7105d7992’ and ‘Erp.Contracts.BO.LaborDtl, Version=10.2.600.0, Culture=neutral, PublicKeyToken=5d3fa3c7105d7992’
The issue seems to be that, when I add a variable that uses a library which has a matching type to a type already defined in the Labor Library, the system doesn’t check whether the type is already defined in the added library so adds the new reference and then it isn’t explicitly specifying the library it is getting the type from.
I think I can get away with using custom code and only specifying the variables in there rather than using the variables in the method, but surely this should be fixed by now!