Thank you for your post.
Custom Web Publishing does not support the Attach File option in FileMaker Server 16.
I cannot move your post, so I recommend posting to the Product Ideas board at: Product Ideas
The Product Ideas board is monitored by Product Management and Development. All entries are read, discussed and considered for possible implementation in a future release.
I see. That's another poorly documented change.
I would say all three are Product Issues rather than Feature Requests, similar to the Set Variable repetition issue.
Removing functionality in a version upgrade is a bug, not a feature.
The Set Variable repetition limitation in FileMaker Pro 16.0.1 was reinstated in FileMaker Pro 16.0.2, and it is documented in Knowledge Base Article #16373. This was changed due to customer requests.
Was there any notice of this change? I don't recall seeing anything.
I'm not sure which change you are talking about (Attach Mail or Set Variable repetition). Either way, there was no notice of this change. It appeared in the Help and Technical Specifications.
For the Set Variable change, customers started asking why this was changed and provided examples why it was needed. Development then reinstated the previous limitation from FileMaker Pro 15 in FileMaker Pro 16.0.2.
Yes, I know. I was referring to the fact that it was unclear if the change to the Set Variable was intentional or not.
The Set Variable issue was reported as a "Product Issue" and 'fixed' in an update. It was initially reported to be unintentional, despite being documented.
Let's just say there are some gray areas in whether change in behavior is a bug or a feature.
1. I believe the point being made was, that it was not included in the Release Notes. All of the mentioned changes in this thread had significant impact on existing custom apps. And should have been noted as a change.
2. I've never seen a 'customer request' flipped back around this fast. I would submit this was a non-intentional change that slipped through.
For any of these changes, there is no technical reason for why it would change. Not even, "we don't think anyone uses that feature anymore".
I don't know why Set Variable would change, but I see FMI having at least a business case for changing CWP.
Of course, reading FMI's intentions is on par with reading entrails. It could simply have been a mistake but a non-generous reading would be that FMI is phasing out CWP in favor of its new API and silently deprecating features is a one way to judge consumer demand.
CWP connections don't count currently count as "Connections" for licensing. The API is currently the same, but it's only a 'trial' and I'm guessing it will be eventually be wrapped into the general licensing limitations.
I would prefer FMI applied some licensing terms to CWP instead of phasing it out but maintaining both CWP and the API could be more trouble than it's worth.
The api licensing could encompass CWP also. It would actually make more sense for them to keep useful functionality. Then get paid for us using it.
Data API (JSON & REST) - is CWP.
Sent from miPhone
>Data API (JSON & REST) - is CWP.
No, not as FM defines those words.
Though I am saying CWP, when I should be saying CWP with PHP. I don't know anything about the XML side.
CWP = Custom Web Publishing. Uses a means (API) to exchange data with FileMaker/FileMaker Server for web publishing:
AppleScript (once upon a time)
CDML/LASSO (once upon a time)
XML (can be called with more than just PHP)
ODBC/JDBC (can be called with any web app that can)
FM API for PHP (a specific set of commands/libraries, using XML to work with PHP)
Data API (using JSON and REST and any web app that can)
NOTE: The "Custom Web Publishing Guide" only mentions the "Custom Web Publishing with XML" and "FileMaker API for PHP" (and even compares them). The "ODBC and JDBC Guide" does mention use with web servers & web applications. The "Data API Guide" talks about web services and web servers.
You are asking for the FM API for PHP to have the access back (and probably the XML - though I haven't tested). Agreed, these should NOT have been taken away. They should be available to any API that is used to web publish with FMS data.
Well, we've been around this before and I still disagree, CWP has a specific meaning referencing technologies that leverage PHP and XML. The FileMaker Data API has a specific meaning referencing technologies that leverage REST architecture. The calls and abilities of each are different. It's useful to have different terms so we can talk about them.
What terms would you use to distinguish the "technology that leverages REST calls in FileMaker" from "the technology that leverages PHP or XML calls in FileMaker"?
I'll continue to use the terms as I understand them to be used in the documentation and the wider community and you can use the terms you prefer.