Author Topic: Integration and Global Fields  (Read 4209 times)

rfrazee

  • Member
  • *
  • Posts: 3
Integration and Global Fields
« on: May 14, 2011, 12:50:43 PM »
I've noticed that the demo file will not create new records. Is that intentional due to demo restrictions?
and;
All fields in the demo are global fields; is the intent to prevent storing the credit card information or is it just because it is a demo. Can the fields be changed to a different type field such as text field if appropriate? Especially when integrated into the another Filemaker solution database?
« Last Edit: May 14, 2011, 02:54:32 PM by rfrazee »

Kevin Clemons

  • Member
  • *
  • Posts: 65
    • Productive Computing
Re: Integration and Global Fields
« Reply #1 on: May 16, 2011, 11:40:41 AM »
You should be able to create a new records like normal. After you select a gateway simply toggle your Status Toolbar back on.

You can modify the demo file in any way as you please, but do allow me to clarify as the plug-in is not a “canned” solution but rather a developers tool. Your FileMaker file actually takes the place of our FileMaker Demo file.
The demo file is given completely open for easy reference or you can copy and paste our existing scripts from our demo file into your solution however you will need to adjust the scripts accordingly in order to specify the correct fields etc.
Kevin Clemons
Products Support Specialist

950 Boardwalk, Suite 205
San Marcos, CA 92078
760-510-1200 xt.105 (voice)  760-510-1991 (fax)

Follow Productive Computing, Inc. on Twitter or FaceBook for the latest updates and product versions.

Melinda DePalma

  • Member
  • *
  • Posts: 179
    • Productive Computing
Re: Integration and Global Fields
« Reply #2 on: May 18, 2011, 11:00:16 AM »
Please alow me to further clarify and answer your question: "can the fields be changed to a different type" ... as yes fields can be changed to a different type. In a live solution the intent would be to have the fields as text field and multiple records (but it is really up to the developer).  Some clients want to store credit cards in FileMaker while others do not.  Globals by they very nature imply no permanent storage.  Text fields by their very nature imply permanent storage.  The plug-in wil work with with fields stored as global text fields or regular text fields.

Hope that helps clarify.

rfrazee

  • Member
  • *
  • Posts: 3
Re: Integration and Global Fields
« Reply #3 on: May 21, 2011, 10:30:56 AM »
Thanks for the information. It's very helpful. I assumed that the globals could be changed to text but wanted to make sure that I wasn't missing something underlying the logic of using globals that wasn't apparent. Didn't want to get into the integration only to discover that there was a limitation revolving around the global field logic.


rfrazee

  • Member
  • *
  • Posts: 3
Re: Integration and Global Fields
« Reply #4 on: May 21, 2011, 11:21:18 AM »
For other readers, I should clarify what we are talking about here. More precisely my original post was actually about whether the fields all had to be globally stored fields not whether they were text or global. Text is a type of field. Global is a storage option. In the demo their are several different types of fields including "text", "number", "calculation", etc. All are stored with global option set to "on".

So my saying "text" vs "global" in the original post might be confusing to some people. I was actually asking "global" or not "global" rather than "text" or "global".

I hope this helps anyone that I may have confused when reading this thread.