Integration
FMChat.Integration History
Hide minor edits - Show changes to output
Added lines 19-20:
->It is also a good idea to start FM Chat when your solution launches as part of the startup script. Please %newwin% [[http://www.youtube.com/watch?v=UR0nuBDnN1k | watch this video]] for the best way to accomplish this.
Changed lines 17-18 from:
->You can [[http://www.youtube.com/watch?v=JgcpTcjvb98 | watch a video walkthrough]] of an integration on youtube.
to:
->You can %newwin% [[http://www.youtube.com/watch?v=JgcpTcjvb98 | watch a video walkthrough]] of an integration on youtube.
Added lines 70-71:
%center% http://www.seedcode.com/rootimages/stikipad/fmchat/ScriptParameters.png
Added lines 57-58:
%center% http://www.seedcode.com/rootimages/stikipad/fmchat/scripts.png
Added lines 49-50:
%center% http://www.seedcode.com/rootimages/stikipad/fmchat/relationship.png
Deleted lines 42-43:
Added lines 47-48:
%center% http://www.seedcode.com/rootimages/stikipad/fmchat/RelationshipGraph.png
Added lines 43-44:
%center% http://www.seedcode.com/rootimages/stikipad/fmchat/RelationshipGraph.png
Changed lines 23-24 from:
'''2. Fields.'''
to:
'''2. File References.'''
->Add two new file references to your file:
->Name the first one "FM Chat" and link it to the file "FMChat.fmp12" then create another one named "FM Chat Go" and link it to the file "FMChat Go.fmp12".
'''3. Fields.'''
->Add two new file references to your file:
->Name the first one "FM Chat" and link it to the file "FMChat.fmp12" then create another one named "FM Chat Go" and link it to the file "FMChat Go.fmp12".
'''3. Fields.'''
Changed lines 37-38 from:
'''3. Table Occurrences.'''
to:
'''4. Table Occurrences.'''
Changed lines 43-44 from:
'''4. Relationships.'''
to:
'''5. Relationships.'''
Changed lines 47-48 from:
'''5. Scripts.'''
to:
'''6. Scripts.'''
Changed lines 53-56 from:
'''6. Layouts Part.'''
->'''6.1''' Paste the chat portal. Open the file "FMChat Integration Example" and navigate to the layout "Chat Portal". Select all and copy the layout contents. Now navigate to the layout based on the table occurrence we are working with in your solution and paste the contents into the layout. You may need to adjust your layout to make room for the portal. It might work best to paste the chat portal off to the side until you can make the necessary layout adjustments in your file.
->'''
to:
'''7. Layouts Part.'''
->'''7.1''' Paste the chat portal. Open the file "FMChat Integration Example" and navigate to the layout "Chat Portal". Select all and copy the layout contents. Now navigate to the layout based on the table occurrence we are working with in your solution and paste the contents into the layout. You may need to adjust your layout to make room for the portal. It might work best to paste the chat portal off to the side until you can make the necessary layout adjustments in your file.
->'''7.1''' Paste the chat portal. Open the file "FMChat Integration Example" and navigate to the layout "Chat Portal". Select all and copy the layout contents. Now navigate to the layout based on the table occurrence we are working with in your solution and paste the contents into the layout. You may need to adjust your layout to make room for the portal. It might work best to paste the chat portal off to the side until you can make the necessary layout adjustments in your file.
Changed lines 59-62 from:
->'''6.2''' Edit the script parameters. In layout mode double click on the "New Chat" button text to edit the button. Click on "Specify" and then "Edit" to edit the script parameter. Here you will need to change the parameter data to match your solution's table occurrence.
->The parameters are name value pairs i.e. "paramName = paramValue". Make sure to leave the names as they are and just modify the values.
->The parameters are name value pairs i.e. "paramName = paramValue". Make sure to leave the names as they are and just modify the values.
to:
->'''7.2''' Edit the script parameters. In layout mode double click on the "New Chat" button text to edit the button. Click on "Specify" and then "Edit" to edit the script parameter. Here you will need to change the parameter data to match your solution's table occurrence.
->The parameters are name value pairs i.e. "paramName = paramValue". Make sure to leave the names as they are and just modify the values. You will need to look closely at how these parameters are set up. An example might be ["entityID = " & Events::EVENT ID MATCH FIELD & " ; " &] What you would replace would be "Events::EVENT ID MATCH FIELD" with whatever your primary key field is. Make sure to leave the "entityID = " intact as well as the " ; " at the end of each line otherwise the parameter will not work.
->The parameters are name value pairs i.e. "paramName = paramValue". Make sure to leave the names as they are and just modify the values. You will need to look closely at how these parameters are set up. An example might be ["entityID = " & Events::EVENT ID MATCH FIELD & " ; " &] What you would replace would be "Events::EVENT ID MATCH FIELD" with whatever your primary key field is. Make sure to leave the "entityID = " intact as well as the " ; " at the end of each line otherwise the parameter will not work.
Deleted lines 14-15:
Changed lines 17-18 from:
->You can watch a video walkthrough of an integration on youtube: [[http://www.youtube.com/watch?v=JgcpTcjvb98]].
to:
->You can [[http://www.youtube.com/watch?v=JgcpTcjvb98 | watch a video walkthrough]] of an integration on youtube.
Changed lines 19-20 from:
->You can [[watch a video walkthrough]],[[http://www.youtube.com/watch?v=JgcpTcjvb98]] of an integration on youtube.
to:
->You can watch a video walkthrough of an integration on youtube: [[http://www.youtube.com/watch?v=JgcpTcjvb98]].
Changed lines 13-14 from:
'''Notes.'''
to:
'''A Few Notes Before We Begin'''
Added lines 19-20:
->You can [[watch a video walkthrough]],[[http://www.youtube.com/watch?v=JgcpTcjvb98]] of an integration on youtube.
Added line 24:
Added line 33:
Changed lines 38-39 from:
'''4. Relationships'''
to:
'''4. Relationships.'''
Changed lines 48-50 from:
'''6. Layouts Part'''
->6.1 Paste the chat portal. Open the file "FMChat Integration Example" and navigate to the layout "Chat Portal". Select all and copy the layout contents. Now navigate to the layout based on the table occurrence we are working with in your solution and paste the contents into the layout. You may need to adjust your layout to make room for the portal. It might work best to paste the chat portal off to the side until you can make the necessary layout adjustments in your file.
->6.1 Paste the chat portal. Open the file "FMChat Integration Example" and navigate to the layout "Chat Portal". Select all and copy the layout contents. Now navigate to the layout based on the table occurrence we are working with in your solution and paste the contents into the layout. You may need to adjust your layout to make room for the portal. It might work best to paste the chat portal off to the side until you can make the necessary layout adjustments in your file.
to:
'''6. Layouts Part.'''
->'''6.1''' Paste the chat portal. Open the file "FMChat Integration Example" and navigate to the layout "Chat Portal". Select all and copy the layout contents. Now navigate to the layout based on the table occurrence we are working with in your solution and paste the contents into the layout. You may need to adjust your layout to make room for the portal. It might work best to paste the chat portal off to the side until you can make the necessary layout adjustments in your file.
->'''6.1''' Paste the chat portal. Open the file "FMChat Integration Example" and navigate to the layout "Chat Portal". Select all and copy the layout contents. Now navigate to the layout based on the table occurrence we are working with in your solution and paste the contents into the layout. You may need to adjust your layout to make room for the portal. It might work best to paste the chat portal off to the side until you can make the necessary layout adjustments in your file.
Changed lines 54-55 from:
->6.2 Edit the script parameters. In layout mode double click on the "New Chat" button text to edit the button. Click on "Specify" and then "Edit" to edit the script parameter. Here you will need to change the parameter data to match your solution's table occurrence.
to:
->'''6.2''' Edit the script parameters. In layout mode double click on the "New Chat" button text to edit the button. Click on "Specify" and then "Edit" to edit the script parameter. Here you will need to change the parameter data to match your solution's table occurrence.
Changed lines 13-18 from:
to:
'''Notes.'''
->Integration works best if all FM Chat files and your Solution file are in the same folder.
->Every table that you would like to integrate with chat will need the following steps completed. Let's start with one table and you can reproduce the steps for any additional tables you would like integrated.
->Integration works best if all FM Chat files and your Solution file are in the same folder.
->Every table that you would like to integrate with chat will need the following steps completed. Let's start with one table and you can reproduce the steps for any additional tables you would like integrated.
Deleted lines 22-26:
Integration works best if all FM Chat files and your Solution file are in the same folder.
Every table that you would like to integrate with chat will need the following steps completed. Let's start with one table and you can reproduce the steps for any additional tables you would like integrated.
Changed lines 25-30 from:
FMC_Type
The calculation for this field should be the data type you are working with in this table for example if this was an invoices table the calculation would just say "invoice" or a purchase orders table would be "Purchase Order". It is not important what goes here it just needs to describe the data type and must be unique. This is used to relate the appropriate chats to your table.
Make sure you check the "Do not store calculation results" checkbox. This option is needed so any records that have already been created will have the value assigned.
The calculation for this field should be the data type you are working with in this table for example if this was an invoices table the calculation would just say "invoice" or a purchase orders table would be "Purchase Order". It is not important what goes here it just needs to describe the data type and must be unique. This is used to relate the appropriate chats to your table.
Make sure you check the "Do not store calculation results" checkbox. This option is needed so any records that have already been created will have the value assigned.
to:
->FMC_Type
->The calculation for this field should be the data type you are working with in this table for example if this was an invoices table the calculation would just say "invoice" or a purchase orders table would be "Purchase Order". It is not important what goes here it just needs to describe the data type and must be unique. This is used to relate the appropriate chats to your table.
->Make sure you check the "Do not store calculation results" checkbox. This option is needed so any records that have already been created will have the value assigned.
->The calculation for this field should be the data type you are working with in this table for example if this was an invoices table the calculation would just say "invoice" or a purchase orders table would be "Purchase Order". It is not important what goes here it just needs to describe the data type and must be unique. This is used to relate the appropriate chats to your table.
->Make sure you check the "Do not store calculation results" checkbox. This option is needed so any records that have already been created will have the value assigned.
Changed lines 34-61 from:
Now we need to add the chats table to your solution. Click the little green plus button in the lower left to create a new occurrence. Select the file "FMChat" as the data source and select the table "Chats". Name the table occurrence "FMC_CHATS_YourTable" (make sure there are no spaces in the table occurrence and do not replace "YourTable" with anything yet, leave it exactly as shown). You can change this name later.
***4. Relationships***
Staying on the Relationships tab, link Your table occurrence to "FMC_CHATS_YourTable" matching the field "FMC_Type" to "entity_Type" and your table's primary key to "ID_Entity".
5. Scripts.
Import the scripts from FMChat Integration Example. When importing, just click the check box beside the folder "FMC Scripts Paste Contents Into Your Solution" and all the scripts within that folder will import.
Note: If any scripts are reported as being "renamed" because of a conflict, quickly scan the imported scripts for names ending "2" and correct them.
6. Layouts Part
6.1 Paste the chat portal. Open the file "FMChat Integration Example" and navigate to the layout "Chat Portal". Select all and copy the layout contents. Now navigate to the layout based on the table occurrence we are working with in your solution and paste the contents into the layout. You may need to adjust your layout to make room for the portal. It might work best to paste the chat portal off to the side until you can make the necessary layout adjustments in your file.
As of this writing there is a bug in filemaker 12 that will prevent conditional formatting from working on pasted objects. To remedy this just enter layout mode double click on the words "Private Chat" in the chat portal to enter the text box (do not edit anything just enter the text box). Now do the same thing on the red "X" delete graphic (there is a little text box covering it). Once both text boxes have been entered you can go back into browse mode and this issue should be resolved.
6.2 Edit the script parameters. In layout mode double click on the "New Chat" button text to edit the button. Click on "Specify" and then "Edit" to edit the script parameter. Here you will need to change the parameter data to match your solution's table occurrence.
The parameters are name value pairs i.e. "paramName = paramValue". Make sure to leave the names as they are and just modify the values.
You will need to change the fields under:
"//ID of this record"
and
"//Display name of this entity"
and
"//Snapshot link file name"
Change out the field values to match your table occurrence. Then make sure to uncomment the calculation by removing "/*" at the beginning and "*/" at the very end. Once complete click "OK" to commit your changes.
Staying on the Relationships tab, link Your table occurrence to "FMC_CHATS_YourTable" matching the field "FMC_Type" to "entity_Type" and your table's primary key to "ID_Entity".
5. Scripts.
Import the scripts from FMChat Integration Example. When importing, just click the check box beside the folder "FMC Scripts Paste Contents Into Your Solution" and all the scripts within that folder will import.
Note: If any scripts are reported as being "renamed" because of a conflict, quickly scan the imported scripts for names ending "2" and correct them.
6. Layouts Part
6.1 Paste the chat portal. Open the file "FMChat Integration Example" and navigate to the layout "Chat Portal". Select all and copy the layout contents. Now navigate to the layout based on the table occurrence we are working with in your solution and paste the contents into the layout. You may need to adjust your layout to make room for the portal. It might work best to paste the chat portal off to the side until you can make the necessary layout adjustments in your file.
As of this writing there is a bug in filemaker 12 that will prevent conditional formatting from working on pasted objects. To remedy this just enter layout mode double click on the words "Private Chat" in the chat portal to enter the text box (do not edit anything just enter the text box). Now do the same thing on the red "X" delete graphic (there is a little text box covering it). Once both text boxes have been entered you can go back into browse mode and this issue should be resolved.
6.2 Edit the script parameters. In layout mode double click on the "New Chat" button text to edit the button. Click on "Specify" and then "Edit" to edit the script parameter. Here you will need to change the parameter data to match your solution's table occurrence.
The parameters are name value pairs i.e. "paramName = paramValue". Make sure to leave the names as they are and just modify the values.
"//ID of this record"
and
"//Display name of this entity"
and
"//Snapshot link file name"
Change out the field values to match your table occurrence. Then make sure to uncomment the calculation by removing "/*" at the beginning and "*/" at the very end. Once complete click "OK" to commit your changes.
to:
->Now we need to add the chats table to your solution. Click the little green plus button in the lower left to create a new occurrence. Select the file "FMChat" as the data source and select the table "Chats". Name the table occurrence "FMC_CHATS_YourTable" (make sure there are no spaces in the table occurrence and do not replace "YourTable" with anything yet, leave it exactly as shown). You can change this name later.
'''4. Relationships'''
->Staying on the Relationships tab, link Your table occurrence to "FMC_CHATS_YourTable" matching the field "FMC_Type" to "entity_Type" and your table's primary key to "ID_Entity".
'''5. Scripts.'''
->Import the scripts from FMChat Integration Example. When importing, just click the check box beside the folder "FMC Scripts Paste Contents Into Your Solution" and all the scripts within that folder will import.
->Note: If any scripts are reported as being "renamed" because of a conflict, quickly scan the imported scripts for names ending "2" and correct them.
'''6. Layouts Part'''
->6.1 Paste the chat portal. Open the file "FMChat Integration Example" and navigate to the layout "Chat Portal". Select all and copy the layout contents. Now navigate to the layout based on the table occurrence we are working with in your solution and paste the contents into the layout. You may need to adjust your layout to make room for the portal. It might work best to paste the chat portal off to the side until you can make the necessary layout adjustments in your file.
->As of this writing there is a bug in filemaker 12 that will prevent conditional formatting from working on pasted objects. To remedy this just enter layout mode double click on the words "Private Chat" in the chat portal to enter the text box (do not edit anything just enter the text box). Now do the same thing on the red "X" delete graphic (there is a little text box covering it). Once both text boxes have been entered you can go back into browse mode and this issue should be resolved.
->6.2 Edit the script parameters. In layout mode double click on the "New Chat" button text to edit the button. Click on "Specify" and then "Edit" to edit the script parameter. Here you will need to change the parameter data to match your solution's table occurrence.
->The parameters are name value pairs i.e. "paramName = paramValue". Make sure to leave the names as they are and just modify the values.
->Change out the field values to match your table occurrence. Then make sure to uncomment the calculation by removing "/*" at the beginning and "*/" at the very end. Once complete click "OK" to commit your changes.
'''4. Relationships'''
->Staying on the Relationships tab, link Your table occurrence to "FMC_CHATS_YourTable" matching the field "FMC_Type" to "entity_Type" and your table's primary key to "ID_Entity".
'''5. Scripts.'''
->Import the scripts from FMChat Integration Example. When importing, just click the check box beside the folder "FMC Scripts Paste Contents Into Your Solution" and all the scripts within that folder will import.
->Note: If any scripts are reported as being "renamed" because of a conflict, quickly scan the imported scripts for names ending "2" and correct them.
'''6. Layouts Part'''
->6.1 Paste the chat portal. Open the file "FMChat Integration Example" and navigate to the layout "Chat Portal". Select all and copy the layout contents. Now navigate to the layout based on the table occurrence we are working with in your solution and paste the contents into the layout. You may need to adjust your layout to make room for the portal. It might work best to paste the chat portal off to the side until you can make the necessary layout adjustments in your file.
->As of this writing there is a bug in filemaker 12 that will prevent conditional formatting from working on pasted objects. To remedy this just enter layout mode double click on the words "Private Chat" in the chat portal to enter the text box (do not edit anything just enter the text box). Now do the same thing on the red "X" delete graphic (there is a little text box covering it). Once both text boxes have been entered you can go back into browse mode and this issue should be resolved.
->6.2 Edit the script parameters. In layout mode double click on the "New Chat" button text to edit the button. Click on "Specify" and then "Edit" to edit the script parameter. Here you will need to change the parameter data to match your solution's table occurrence.
->The parameters are name value pairs i.e. "paramName = paramValue". Make sure to leave the names as they are and just modify the values.
->Change out the field values to match your table occurrence. Then make sure to uncomment the calculation by removing "/*" at the beginning and "*/" at the very end. Once complete click "OK" to commit your changes.
Changed lines 13-19 from:
***1. Backup your
Really.
to:
'''1. Backup your file.'''
->Really.
Changed line 23 from:
to:
'''2. Fields.'''
Changed lines 25-26 from:
to:
FMC_Type
Changed lines 31-33 from:
3. Table Occurrences.
Select File / Manage / Database and navigate to the Relationships tab where you can see the "relationship graph" for your file. Click the little green plus button in the lower left to create a new occurrence. Select the file "FMChat" as the data source and select the table "System". Name the table occurrence "FMC_SYSTEM" (make sure there are no spaces in the table occurrence name). You can change this name later. This table is a utility table that stores global data. It will only ever need to have one occurrence in your solution.
Select File / Manage / Database and navigate to the Relationships tab where you can see the "relationship graph" for your file. Click the little green plus button in the lower left to create a new occurrence. Select the file "FMChat" as the data source and select the table "System". Name the table occurrence "FMC_SYSTEM" (make sure there are no spaces in the table occurrence name). You can change this name later. This table is a utility table that stores global data. It will only ever need to have one occurrence in your solution.
to:
'''3. Table Occurrences.'''
->Select File / Manage / Database and navigate to the Relationships tab where you can see the "relationship graph" for your file. Click the little green plus button in the lower left to create a new occurrence. Select the file "FMChat" as the data source and select the table "System". Name the table occurrence "FMC_SYSTEM" (make sure there are no spaces in the table occurrence name). You can change this name later. This table is a utility table that stores global data. It will only ever need to have one occurrence in your solution.
->Select File / Manage / Database and navigate to the Relationships tab where you can see the "relationship graph" for your file. Click the little green plus button in the lower left to create a new occurrence. Select the file "FMChat" as the data source and select the table "System". Name the table occurrence "FMC_SYSTEM" (make sure there are no spaces in the table occurrence name). You can change this name later. This table is a utility table that stores global data. It will only ever need to have one occurrence in your solution.
Changed lines 13-29 from:
-> Let's assume that you are integrating FMChat and attaching it to an Invoices table:
-> Create a file reference to the FMChat file called "FM Chat". \\
Edit your startup script to open the FMChat file. \\
Create a table occurrence from the FMChat table System called "FMC_System". \\
Create a field in the Invoices table. Name the field "FMC_EntityType" and make it an unstored calculation field with data of "Invoice". \\
Create a table occurrence from the FMChat table "Chats" called "FMC_Invoices_CHATS" \\
Create a relationship between the "Invoices" table and the "FMC_Invoices_CHATS" table, linking the ID field from Invoices to the ID_Entity field in FMC_Invoices_CHATS and the "FMC_EntityType" field from Invoices to the "entity_Type" field in FMC_Invoices_CHATS. \\
Copy the script folder called "FMC Scripts Paste Contents Into Your Solution" from the Test Solution file and paste it into your database file. \\
Copy the Chat portal from the Test Solution file and paste it into your solution (in this case on the layout for your invoices table. \\
Update the lastPost_Display field in the chat portal to point to the appropriate table occurrence that you created earlier. \\
Double click on the lastPost_Display field to edit the script parameters being passed with that button. The parameters will need to be updated to reflect the table occurrence that the portal is connected to. \\
Update the Send Records Being Browsed button to make the script parameters being passed to reflect the table occurrence associated with the chat portal. \\
Update the script parameters being passed with the "Delete" button to reflect the table occurrence associated with the chat portal. \\
Update the script parameters being passed with the "New Chat" button to reflect the table occurrence associated with the chat portal.
to:
# Ordered list
***1. Backup your file.***
Really.
Integration works best if all FM Chat files and your Solution file are in the same folder.
Every table that you would like to integrate with chat will need the following steps completed. Let's start with one table and you can reproduce the steps for any additional tables you would like integrated.
***2. Fields.***
->Add a new calculation field to your table (Calculation result is Text):
->FMC_Type
The calculation for this field should be the data type you are working with in this table for example if this was an invoices table the calculation would just say "invoice" or a purchase orders table would be "Purchase Order". It is not important what goes here it just needs to describe the data type and must be unique. This is used to relate the appropriate chats to your table.
Make sure you check the "Do not store calculation results" checkbox. This option is needed so any records that have already been created will have the value assigned.
3. Table Occurrences.
Select File / Manage / Database and navigate to the Relationships tab where you can see the "relationship graph" for your file. Click the little green plus button in the lower left to create a new occurrence. Select the file "FMChat" as the data source and select the table "System". Name the table occurrence "FMC_SYSTEM" (make sure there are no spaces in the table occurrence name). You can change this name later. This table is a utility table that stores global data. It will only ever need to have one occurrence in your solution.
Now we need to add the chats table to your solution. Click the little green plus button in the lower left to create a new occurrence. Select the file "FMChat" as the data source and select the table "Chats". Name the table occurrence "FMC_CHATS_YourTable" (make sure there are no spaces in the table occurrence and do not replace "YourTable" with anything yet, leave it exactly as shown). You can change this name later.
***4. Relationships***
Staying on the Relationships tab, link Your table occurrence to "FMC_CHATS_YourTable" matching the field "FMC_Type" to "entity_Type" and your table's primary key to "ID_Entity".
5. Scripts.
Import the scripts from FMChat Integration Example. When importing, just click the check box beside the folder "FMC Scripts Paste Contents Into Your Solution" and all the scripts within that folder will import.
Note: If any scripts are reported as being "renamed" because of a conflict, quickly scan the imported scripts for names ending "2" and correct them.
6. Layouts Part
6.1 Paste the chat portal. Open the file "FMChat Integration Example" and navigate to the layout "Chat Portal". Select all and copy the layout contents. Now navigate to the layout based on the table occurrence we are working with in your solution and paste the contents into the layout. You may need to adjust your layout to make room for the portal. It might work best to paste the chat portal off to the side until you can make the necessary layout adjustments in your file.
As of this writing there is a bug in filemaker 12 that will prevent conditional formatting from working on pasted objects. To remedy this just enter layout mode double click on the words "Private Chat" in the chat portal to enter the text box (do not edit anything just enter the text box). Now do the same thing on the red "X" delete graphic (there is a little text box covering it). Once both text boxes have been entered you can go back into browse mode and this issue should be resolved.
6.2 Edit the script parameters. In layout mode double click on the "New Chat" button text to edit the button. Click on "Specify" and then "Edit" to edit the script parameter. Here you will need to change the parameter data to match your solution's table occurrence.
The parameters are name value pairs i.e. "paramName = paramValue". Make sure to leave the names as they are and just modify the values.
You will need to change the fields under:
"//ID of this record"
and
"//Display name of this entity"
and
"//Snapshot link file name"
Change out the field values to match your table occurrence. Then make sure to uncomment the calculation by removing "/*" at the beginning and "*/" at the very end. Once complete click "OK" to commit your changes.
***1. Backup your file.***
Really.
Integration works best if all FM Chat files and your Solution file are in the same folder.
Every table that you would like to integrate with chat will need the following steps completed. Let's start with one table and you can reproduce the steps for any additional tables you would like integrated.
***2. Fields.***
->Add a new calculation field to your table (Calculation result is Text):
->FMC_Type
The calculation for this field should be the data type you are working with in this table for example if this was an invoices table the calculation would just say "invoice" or a purchase orders table would be "Purchase Order". It is not important what goes here it just needs to describe the data type and must be unique. This is used to relate the appropriate chats to your table.
Make sure you check the "Do not store calculation results" checkbox. This option is needed so any records that have already been created will have the value assigned.
3. Table Occurrences.
Select File / Manage / Database and navigate to the Relationships tab where you can see the "relationship graph" for your file. Click the little green plus button in the lower left to create a new occurrence. Select the file "FMChat" as the data source and select the table "System". Name the table occurrence "FMC_SYSTEM" (make sure there are no spaces in the table occurrence name). You can change this name later. This table is a utility table that stores global data. It will only ever need to have one occurrence in your solution.
Now we need to add the chats table to your solution. Click the little green plus button in the lower left to create a new occurrence. Select the file "FMChat" as the data source and select the table "Chats". Name the table occurrence "FMC_CHATS_YourTable" (make sure there are no spaces in the table occurrence and do not replace "YourTable" with anything yet, leave it exactly as shown). You can change this name later.
***4. Relationships***
Staying on the Relationships tab, link Your table occurrence to "FMC_CHATS_YourTable" matching the field "FMC_Type" to "entity_Type" and your table's primary key to "ID_Entity".
5. Scripts.
Import the scripts from FMChat Integration Example. When importing, just click the check box beside the folder "FMC Scripts Paste Contents Into Your Solution" and all the scripts within that folder will import.
Note: If any scripts are reported as being "renamed" because of a conflict, quickly scan the imported scripts for names ending "2" and correct them.
6. Layouts Part
6.1 Paste the chat portal. Open the file "FMChat Integration Example" and navigate to the layout "Chat Portal". Select all and copy the layout contents. Now navigate to the layout based on the table occurrence we are working with in your solution and paste the contents into the layout. You may need to adjust your layout to make room for the portal. It might work best to paste the chat portal off to the side until you can make the necessary layout adjustments in your file.
As of this writing there is a bug in filemaker 12 that will prevent conditional formatting from working on pasted objects. To remedy this just enter layout mode double click on the words "Private Chat" in the chat portal to enter the text box (do not edit anything just enter the text box). Now do the same thing on the red "X" delete graphic (there is a little text box covering it). Once both text boxes have been entered you can go back into browse mode and this issue should be resolved.
6.2 Edit the script parameters. In layout mode double click on the "New Chat" button text to edit the button. Click on "Specify" and then "Edit" to edit the script parameter. Here you will need to change the parameter data to match your solution's table occurrence.
The parameters are name value pairs i.e. "paramName = paramValue". Make sure to leave the names as they are and just modify the values.
You will need to change the fields under:
"//ID of this record"
and
"//Display name of this entity"
and
"//Snapshot link file name"
Change out the field values to match your table occurrence. Then make sure to uncomment the calculation by removing "/*" at the beginning and "*/" at the very end. Once complete click "OK" to commit your changes.
Changed lines 7-8 from:
Learn more about [[Data Detectors]]
to:
-> Learn more about [[Data Detectors]]
Changed lines 5-6 from:
-> coming soon
to:
-> The simplest way to use FM Chat with your solutions is through data detectors. FM Chat runs on your host or server alongside your other FileMaker solutions as its own hosted file. When you need to jump from a chat to a particular record in your solution, you'd use a data detector to let you create a link to that record (or a link that would call a script in your solution).
Learn more about [[Data Detectors]]
Learn more about [[Data Detectors]]
Changed lines 11-12 from:
-> The big advantage of linking is that on a given record in your solution you can have a portal of chats pertaining to that record show up ''on'' that record in your file. Here's how to do it:
to:
-> Again, FM Chat runs as a separate file in your FileMaker host or server. The big advantage of linking is that on a given record in your solution you can have a portal of chats pertaining to that record show up ''on'' that record in your file. Here's how to do it:
Changed line 27 from:
Update the script parameters being passed with the "New Chat" button to reflect the table occurrence associated with the chat portal. \\
to:
Update the script parameters being passed with the "New Chat" button to reflect the table occurrence associated with the chat portal.
Changed lines 7-8 from:
'''Linking Chats to Entities'''
to:
'''Linking Chats to Entities (Records)'''
Changed lines 13-27 from:
Let's assume that you are integrating FMChat and attaching it to an Invoices table:
Create a file reference to the FMChat file called "FM Chat".
Edit your startup script to open the FMChat file.
Create a table occurrence from the FMChat table System called "FMC_System".
Create a field in the Invoices table. Name the field "FMC_EntityType" and make it an unstored calculation field with data of "Invoice".
Create a table occurrence from the FMChat table "Chats" called "FMC_Invoices_CHATS"
Create a relationship between the "Invoices" table and the "FMC_Invoices_CHATS" table, linking the ID field from Invoices to the ID_Entity field in FMC_Invoices_CHATS and the "FMC_EntityType" field from Invoices to the "entity_Type" field in FMC_Invoices_CHATS.
Copy the script folder called "FMC Scripts Paste Contents Into Your Solution" from the Test Solution file and paste it into your database file.
Copy the Chat portal from the Test Solution file and paste it into your solution (in this case on the layout for your invoices table.
Update the lastPost_Display field in the chat portal to point to the appropriate table occurrence that you created earlier.
Double click on the lastPost_Display field to edit the script parameters being passed with that button. The parameters will need to be updated to reflect the table occurrence that the portal is connected to.
Update the Send Records Being Browsed button to make the script parameters being passed to reflect the table occurrence associated with the chat portal.
Update the script parameters being passed with the "Delete" button to reflect the table occurrence associated with the chat portal.
Update the script parameters being passed with the "New Chat" button to reflect the table occurrence associated with the chat portal.
Create a file reference to the FMChat file called "FM Chat".
to:
-> Let's assume that you are integrating FMChat and attaching it to an Invoices table:
-> Create a file reference to the FMChat file called "FM Chat". \\
Edit your startup script to open the FMChat file. \\
Create a table occurrence from the FMChat table System called "FMC_System". \\
Create a field in the Invoices table. Name the field "FMC_EntityType" and make it an unstored calculation field with data of "Invoice". \\
Create a table occurrence from the FMChat table "Chats" called "FMC_Invoices_CHATS" \\
Create a relationship between the "Invoices" table and the "FMC_Invoices_CHATS" table, linking the ID field from Invoices to the ID_Entity field in FMC_Invoices_CHATS and the "FMC_EntityType" field from Invoices to the "entity_Type" field in FMC_Invoices_CHATS. \\
Copy the script folder called "FMC Scripts Paste Contents Into Your Solution" from the Test Solution file and paste it into your database file. \\
Copy the Chat portal from the Test Solution file and paste it into your solution (in this case on the layout for your invoices table. \\
Update the lastPost_Display field in the chat portal to point to the appropriate table occurrence that you created earlier. \\
Double click on the lastPost_Display field to edit the script parameters being passed with that button. The parameters will need to be updated to reflect the table occurrence that the portal is connected to. \\
Update the Send Records Being Browsed button to make the script parameters being passed to reflect the table occurrence associated with the chat portal. \\
Update the script parameters being passed with the "Delete" button to reflect the table occurrence associated with the chat portal. \\
Update the script parameters being passed with the "New Chat" button to reflect the table occurrence associated with the chat portal. \\
-> Create a file reference to the FMChat file called "FM Chat". \\
Edit your startup script to open the FMChat file. \\
Create a table occurrence from the FMChat table System called "FMC_System". \\
Create a field in the Invoices table. Name the field "FMC_EntityType" and make it an unstored calculation field with data of "Invoice". \\
Create a table occurrence from the FMChat table "Chats" called "FMC_Invoices_CHATS" \\
Create a relationship between the "Invoices" table and the "FMC_Invoices_CHATS" table, linking the ID field from Invoices to the ID_Entity field in FMC_Invoices_CHATS and the "FMC_EntityType" field from Invoices to the "entity_Type" field in FMC_Invoices_CHATS. \\
Copy the script folder called "FMC Scripts Paste Contents Into Your Solution" from the Test Solution file and paste it into your database file. \\
Copy the Chat portal from the Test Solution file and paste it into your solution (in this case on the layout for your invoices table. \\
Update the lastPost_Display field in the chat portal to point to the appropriate table occurrence that you created earlier. \\
Double click on the lastPost_Display field to edit the script parameters being passed with that button. The parameters will need to be updated to reflect the table occurrence that the portal is connected to. \\
Update the Send Records Being Browsed button to make the script parameters being passed to reflect the table occurrence associated with the chat portal. \\
Update the script parameters being passed with the "Delete" button to reflect the table occurrence associated with the chat portal. \\
Update the script parameters being passed with the "New Chat" button to reflect the table occurrence associated with the chat portal. \\
Changed lines 3-4 from:
Using Data Detectors
to:
'''Using Data Detectors'''
Changed lines 7-8 from:
Linking Chats to Entities
to:
'''Linking Chats to Entities'''
Changed lines 13-15 from:
to:
Let's assume that you are integrating FMChat and attaching it to an Invoices table:
Create a file reference to the FMChat file called "FM Chat".
Create a file reference to the FMChat file called "FM Chat".
Added lines 1-27:
!! How do I link FM Chat to my own files & records?
Using Data Detectors
-> coming soon
Linking Chats to Entities
-> The big advantage of linking is that on a given record in your solution you can have a portal of chats pertaining to that record show up ''on'' that record in your file. Here's how to do it:
> > Rough version. Very rough.
-> Let's assume that you are integrating FMChat and attaching it to an Invoices table:
-> Create a file reference to the FMChat file called "FM Chat".
Edit your startup script to open the FMChat file.
Create a table occurrence from the FMChat table System called "FMC_System".
Create a field in the Invoices table. Name the field "FMC_EntityType" and make it an unstored calculation field with data of "Invoice".
Create a table occurrence from the FMChat table "Chats" called "FMC_Invoices_CHATS"
Create a relationship between the "Invoices" table and the "FMC_Invoices_CHATS" table, linking the ID field from Invoices to the ID_Entity field in FMC_Invoices_CHATS and the "FMC_EntityType" field from Invoices to the "entity_Type" field in FMC_Invoices_CHATS.
Copy the script folder called "FMC Scripts Paste Contents Into Your Solution" from the Test Solution file and paste it into your database file.
Copy the Chat portal from the Test Solution file and paste it into your solution (in this case on the layout for your invoices table.
Update the lastPost_Display field in the chat portal to point to the appropriate table occurrence that you created earlier.
Double click on the lastPost_Display field to edit the script parameters being passed with that button. The parameters will need to be updated to reflect the table occurrence that the portal is connected to.
Update the Send Records Being Browsed button to make the script parameters being passed to reflect the table occurrence associated with the chat portal.
Update the script parameters being passed with the "Delete" button to reflect the table occurrence associated with the chat portal.
Update the script parameters being passed with the "New Chat" button to reflect the table occurrence associated with the chat portal.
Using Data Detectors
-> coming soon
Linking Chats to Entities
-> The big advantage of linking is that on a given record in your solution you can have a portal of chats pertaining to that record show up ''on'' that record in your file. Here's how to do it:
> > Rough version. Very rough.
-> Let's assume that you are integrating FMChat and attaching it to an Invoices table:
-> Create a file reference to the FMChat file called "FM Chat".
Edit your startup script to open the FMChat file.
Create a table occurrence from the FMChat table System called "FMC_System".
Create a field in the Invoices table. Name the field "FMC_EntityType" and make it an unstored calculation field with data of "Invoice".
Create a table occurrence from the FMChat table "Chats" called "FMC_Invoices_CHATS"
Create a relationship between the "Invoices" table and the "FMC_Invoices_CHATS" table, linking the ID field from Invoices to the ID_Entity field in FMC_Invoices_CHATS and the "FMC_EntityType" field from Invoices to the "entity_Type" field in FMC_Invoices_CHATS.
Copy the script folder called "FMC Scripts Paste Contents Into Your Solution" from the Test Solution file and paste it into your database file.
Copy the Chat portal from the Test Solution file and paste it into your solution (in this case on the layout for your invoices table.
Update the lastPost_Display field in the chat portal to point to the appropriate table occurrence that you created earlier.
Double click on the lastPost_Display field to edit the script parameters being passed with that button. The parameters will need to be updated to reflect the table occurrence that the portal is connected to.
Update the Send Records Being Browsed button to make the script parameters being passed to reflect the table occurrence associated with the chat portal.
Update the script parameters being passed with the "Delete" button to reflect the table occurrence associated with the chat portal.
Update the script parameters being passed with the "New Chat" button to reflect the table occurrence associated with the chat portal.
