Skip to main content

Notifications

Microsoft Dynamics GP (Archived)

Bank Transaction Entry Integration

Posted on by 1,960

I am getting this error when trying to import a bank transaction in integration manager (GP2013).  What does it mean?

DOC 1 ERROR: Unimplemented cast from Btype 'BROWSETYPE_UNKNOWN'

*This post is locked for comments

  • Amit Thakkar Profile Picture
    Amit Thakkar on at
    RE: Bank Transaction Entry Integration

    I have installed Sp2 on IM and now version is 1488.

    Now error for IM in Bank transaction has (GP2013) gone.

    SP2 Fixed following

    ervice Pack 2

    Type Issue description

    Fix 68296 When running a Bank Transaction Integration, you receive the following error.

    Doc 1 Error: Unimplemented case from Btype 'BROWSETYPE_UNKNOWN’.

    Fix 69893 The Employee Pay Code integration causes the following error.

    DEXTERITY_IM_MACRO_INACTIVE_HIT (error DEXTERITY_IM_MACRO_INACTIVE_HIT): MoveTo field 'Employee ID'. 60120

    Fix 69798 When running a Payroll Integration using negative numbers for deductions you receiving the following error.

    "DOC 1 ERROR: Overflow in assigning value -8 to Currency field 'Entries.Amount' -- Range is -922,337,203,685,477.5808 to

    922,337,203,685,477.5807 - Input string was not in a correct format."

  • Peggy Paskawati Profile Picture
    Peggy Paskawati 5 on at
    RE: Bank Transaction Entry Integration

    To solve this case, I installed Integration Manager 10.0 version and I did the bank transaction entry integration to GP 2013 using it. It worked.

    Hopefully it works for you too.

  • Suggested answer
    sueconrod Profile Picture
    sueconrod 335 on at
    RE: Bank Transaction Entry Integration

    Your answer came from other uses with the same issue:

    Posted by Scott Witteveen

    onTue, Apr 30 2013 2:35 PM

    I was informed that there is a bug in IM for GP2013 and that it will be addressed in a future service pack.  If this is the only error you get, the transactions most likely integrated, but should be verified by reviewing the transactions in the checkbook.  One additional workaround step that support suggested was to increase the Maximum number of errors and warnings to a number greater than the number of transactions to be integrated.  Hopefully that helps, Scott

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,253 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,188 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans