By using this website, you agree to our Terms of Use (click here)
So I am stumped...I copied and modified the ACU Import AP Bills Import Scenario. When I run the import when I have 'Activate Migration Mode' checked in Account Payables Preferences, I get an error that tells me the Save button is disabled. If I uncheck the 'Activate Migration Mode', the import scenario works. The only difference between the two is that you have to put in the balance of the bill if migration mode is checked.
Looking for ideas.
Similar issue... makes no sense to import bills with $0 balance. Did you figure anything out? I could sure use an insight here.
I noticed that the Hold field is listed twice which looks funny to me. Other than that, nothing looks strange to me. Have you tried deactivating everything except for the few required fields to see if it runs? If it does, you could activate one field at a time to see where the offending field is.
I had this same exact problem. No matter what I tried, I could not get the document to take the document off hold automatically.
I solved this with a small customization. Just tested and works great! I created a Graph Extension for APInvoiceEntry and JournalEntry (journals also have the same problem. This adds an action to take the transaction off hold when it reaches a balanced state:
namespace PX.Objects.AP
{
public class APInvoiceEntry_Extension : PXGraphExtension<APInvoiceEntry>
{
public PXAction<APInvoice> TakeOffHold;
[PXButton(CommitChanges=true)]
[PXUIField(DisplayName="Take Off Hold")]
public IEnumerable takeOffHold(PXAdapter adapter)
{
Base.Document.Current.Hold = !(Base.Document.Current.CuryLineTotal == Base.Document.Current.CuryOrigDocAmt);
Base.Document.Update(Base.Document.Current);
return adapter.Get();
}
}
} namespace PX.Objects.GL
{
public class JournalEntry_Extension : PXGraphExtension<JournalEntry>
{
public PXAction<Batch> TakeOffHold;
[PXButton(CommitChanges=true)]
[PXUIField(DisplayName="Take Off Hold")]
public IEnumerable takeOffHold(PXAdapter adapter)
{
Base.BatchModule.Current.Hold = !(Base.BatchModule.Current.CuryDebitTotal == Base.BatchModule.Current.CuryCreditTotal);
Base.BatchModule.Update(Base.BatchModule.Current);
return adapter.Get();
}
}
}
Then in the import scenario, I added above my <Action:Save> to run my action <Action:Take Off Hold>.
Works beautifully! Saves me from having to import on hold first, and then import again off hold.
So the problem was that I needed to remove a customization that the customer had on their system (nothing really to do with AP).
When I unpublished the customization, it worked just fine. Since this was only going to be run at the time of conversion that worked for me.
Online Members
