Several of our clients have experienced the infamous 7175 error and the subsequent “Tried to call a method in an invalid procedure. (7224)” error.  This error normally indicates a broken network connection between the client machine and the server, so after a user sees this error, Epicor will stop functioning withal.  For users with elusive but persistent network hiccups, this

How have we at Deft Flux made life easier by implementing elegant solutions to real business requirements?  Herewith, we present two examples. Company A needs to produce an XML file for the Job Order Interface of its Trumpf Inventory Manager Machine.  Company A also needs to produce a tab-delimited advanced ship notice (ASN) for upload to a customer’s system.  Both

We often hear from someone who needs to log changes to data in his business system. Perhaps a production supervisor wants to know when the description of a part was changed or a human resources manager wants a record of everyone’s pay rate changes. Maybe the human resources manager also wants to be notified by e-mail every time the pay

In the world of Epicor, most customer modifications (Dashboards, BAQs, Customizations, etc.) can be individually exported to a file and thus imported one at a time.  This is a convenient way to make a quick modification and move it from Pilot or Test up to Live.  Not all modifications are created equal, however.  A Dashboard cannot be imported to update

At Deft Flux, we are curing business information headaches, and we are doing it because we care.  Here is an example. Epicor has several different paths whereby one may create a customization.  So far, we have found the Business Process Management (BPM) method directive to be the most useful.  Why?