CodePartners - Software Development - Dallas, Texas Software Development - Sage Accpac Customization - SageCRM Customization
Login
pay invoice online  |  remote assistance  |  
  • INTERNET APPLICATION DEVELOPMENT

    • Services
      • Web Application Development
      • Mobile Applications
      • Integration Solutions
      • Staff Augmentation
    • Technologies
    • How we work
    • About us
    • Success stories
    • Blog
  • MID MARKET ERP DEVELOPMENT

    • Intacct
    • Sage CRM
    • Sage
    • Sage Component Catalog
    • How We Work
    • About Us
    • Success Stories
    • Blog

Blog

CodePartners Blog

rss


How to Bypass Smart Rule Warnings

SHARE THIS
Facebook twitter linkedin Print Print
Print Email

by Joe Zhou

Prior to attending Intacct Advantage 2013, our team wrapped up our first Intacct and Sage CRM Integration project. 

This project began out of necessity for the sales team to initialize an opportunity in Sage CRM and automatically promote this opportunity to Intacct once the opportunity becomes a project. To create a project in Intacct, the sales team begins the workflow by initializing the opportunity in Sage CRM.

During the development phase we discovered that when we created a project directly in Intacct, without creating a corresponding opportunity in Sage CRM, the workflow broke down. So, I created a Smart Rule, referenced in example 3 from my recent blog post. This Smart Rule warns the user about the broken workflow before he or she attempts to create a project. However, when the integration code hits the Smart Rule, an error returned noting a project cannot be created within the program due to this Smart Rule.  

My research found two ways to bypass the warning triggered by the Smart Rule:  

1. Create a dedicated user account for web service calls only and add logic to validate if the user is present in the condition of the Smart Rule. This does not trigger the Smart Rule if the dedicated user account is detected. Then, the web service call goes through without warning. 


Type:  Warning

Events:  Add

Condition: {!CURRENTUSER.LOGINID!} == "platform"

Error Message:Warning goes here

 

2. Use a flag in the XML call, which disables the validation rule. However, according to Intacct API documentation, the flag method only is available within the create_sotransaction method. Therefore, this process is truly not an option that can be applied to the project object. 

I look forward to sharing with you these Intacct circumstances so that you may be aware of these challenges. My hope is this attribute is available in the future for customers. In the meantime, if you have a work-around to this issue, please leave your comments here.  






Comments are closed.
On November 20, 2013 in Development, Integration, Web application, Web Development by Lori Thomas
Tagged With: Sage CRM, Intacct, Intacct Integration, Intacct Platform Services, Smart Rule / 2144 Views

Search

Categories

  • General (166) rss
  • Development (158) rss
  • Success Stories (40) rss
  • Products (29) rss
  • Uncategorized (18) rss
  • BTerrell Group (5) rss
  • Project Management (22) rss
  • Web Development (57) rss
  • Web application (33) rss
  • Integration (19) rss
  • Mobile Development (7) rss

Archives

  • 2015
    • January (5)
    • February (7)
    • March (6)
    • April (5)
    • May (2)
  • 2014
    • January (13)
    • February (12)
    • March (13)
    • April (12)
    • May (11)
    • June (12)
    • July (11)
    • August (13)
    • September (10)
    • October (8)
    • November (6)
    • December (4)
  • 2013
    • April (73)
    • May (22)
    • June (20)
    • July (20)
    • August (22)
    • September (19)
    • October (13)
    • November (12)
    • December (7)

Tags

.NET Accpac app development application customization application development automation Azure C# cloud components Crystal Reports customization development ERP general ledger HTML5 Intacct Intacct Platform Services integration JQuery load balancer mass update mobile development OCR Order Entry outsourcing PO pricing product development project management REST Sage 300 ERP Sage CRM software integration trigger user interface Visual Studio web application web development website development Workforce Go! .NET ACA accpac Ajax Amazon AP invoices application development Arxis ASP.NET automation Axure BTerrell Group C# Cloud computing CodePartners Constant Contact credit card processing CRM crystal reports custom software Customer Service Customization Delete team project design phase Development doc-link DRILLDWNLK ERP event Excel GLAFS Intacct Intacct Advantage Intacct Platform Services Integration Java script JavaScript jQuery Kerr Consulting LinkedIn Microsoft MSSQL Offshoring outsourcing payroll PCI compliance PCI-DSS Pivot PJC project management sage Sage 300 Sage 300 ERP Sage Accpac ERP Sage CRM Smart Rule social media software testing SQL SQL Query SQL Server staff augmentation sub-ledger success success story TFS Trouble shooting UI design Visual Studio WCF Web API web application web design web development Webinar website Windows Windows Azure XML
Email this article from Codepartners.com
Separate multiple addresses with commas(,)
To: *   Copy me
Subject:
From: *
Message:
ABOUT US / CONTACT US / NEWS & EVENTS
CodePartners / 16200 Addison Rd. STE 270 / Addison, Texas 75001 / Phone: 214-647-2611 / Toll Free: 866-647-2611 / Fax: 214-647-2612 / info@codepartners.com
© 2006 - 2015 codepartners.com All Rights Reserved.