Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 07/15/19 in Blog Entries

  1. 6 points
    Cet article FileMaker 19 : entrée dans un nouveau monde est apparu en premier sur 1-more-thing. >>> Lire la suite… <<<
  2. 2 points
    Aujourd’hui, c’est graphe des liens… Je vais vous montrer que ce graphe des liens reflète vos décisions (ou choix) dans les options de rubrique. Prenons les cas d’une gestion de facturation. Nous avons, pour ce type de gestion, au moins quatre tables : CLIENTS, FACTURES, LIGNES et PRODUITS. Après une longue, très longue, analyse, nous avons le schéma relationnel suivant : J’ai utilisé le code couleur suivant : Rouge pour les clefs primaires, rubriques ne contenant que des valeurs uniques dans une table, permettant d’identifier sûrement un enregistrement. Vert pour les clefs étrangères, rubriques servant à « attacher » un ou plusieurs enregistrements à un enregistrement d’une autre table. Nous remarquons que le lien entre les tables CLIENTS et FACTURES est de type 1 vers N, ou N vers 1 suivant qu’on démarre de la table FACTURES. Sur le schéma relationnel, nous le symbolisons par : Et nous retrouvons ce type de lien sur l’ensemble de notre schéma relationnel. Une fois le schéma relationnel établi sur le papier, nous pouvons passer à la réalisation sous FileMaker Pro. Je vous passe les détails pour la réalisation du fichier, des tables, des rubriques et du graphe des liens. Là, vous devriez remarquer que je parle de « graphe des liens » et non plus de « schéma relationnel ». Regarder la figure suivante : C’est le graphe réalisé avec FileMaker Pro, regardons d’un peu plus près le lien entre les occurrences de tables CLIENTS et FACTURES : Si vous regardez bien, vous remarquerez que FileMaker schématise le lien avec une représentation de lien de type N vers N : Pourquoi diable FileMaker Pro nous représente un lien de type N vers N alors que nous avons normalement une relation entre CLIENTS et FACTURES de type 1 vers N ? De plus, nous avons aucun moyen sur le graphe des liens de définir le type de lien. En fait, ce n’est pas sur le graphe des lien que nous pouvons définir le type de lien. Car le graphe des liens de FileMaker Pro reflète les options appliquées aux rubriques. Occupons-nous de la table CLIENTS. La rubrique N° client est, sur notre schéma relationnel, une clef primaire, à savoir qu’elle doit contenir une valeur unique. Nous pouvons alors définir une option de contrôle sur cette rubrique de type Unique : Fichier > Gérer > Base de données… ; Onglet Rubriques ; Table CLIENTS ; Sélection de la rubrique N° client, puis bouton Options… ; Onglet Contrôle ; Option Unique ; Validation. Si maintenant, nous allons voir le graphe des liens, nous nous apercevons que le type de lien schématisé par FileMaker Pro à changé : Nous avons bien maintenant un lien de type 1 vers N et non plus un lien de type N vers N. Si maintenant nous aurions choisi une option d’entrée automatique de type numéro de série au lieu d’une option de contrôle de type unique pour la rubrique N° client, FileMaker Pro aurait schématisé le lien de type 1 vers N. Nous voyons donc que FileMaker Pro change le type de lien dans le graphe des liens pour tenir compte, ou pour refléter, les options apportées aux rubriques. C’est donc un moyen simple pour savoir si on n’a pas oublié une option sur une rubrique. Il reste encore une autre schématisation. Imaginons que nous souhaitons avoir la liste des factures pour une année donnée pour chaque client. Nous ajoutons alors une rubrique Année, de type nombre, dans la table FACTURES, pourquoi pas de type calcul, avec un résultat de type nombre et avec la formule ANNEE( Date ). Ajoutons maintenant une rubrique Année dans la table CLIENTS, de type nombre, mais avec l’option Globale, pour nous permettre d’avoir la même année quelque soit l’enregistrement client. Établissons, maintenant un lien entre les deux nouvelles rubriques, et nous obtenons le schéma suivant : Évidemment, pour éviter de modifier le lien existant entre les occurrences de tables CLIENTS et FACTURES, nous devons donc ajouter une deuxième occurrences de tables pour FACTURES, nommée FACTURES ANNÉE. Et là, on voit que le type de lien schématisé par FileMaker Pro est différent, nous avons un lien du type : C’est un type de lien qui nous informe que la rubrique Année de la table CLIENTS a l’option stockage global. Mais cela signifie aussi que le lien n’est pas bi-directionnel mais uni-directionnel. C’est-à-dire que la table CLIENTS peut connaître les enregistrements de l’occurrence de table FACTURES ANNÉE, alors que l’occurrence de table FACTURES ANNÉE ne peut pas connaître les enregistrements de CLIENTS. Voilà pourquoi je vous indiquais en introduction que le graphe des liens de FileMaker Pro reflètes les options de rubriques. C’est tout pour aujourd’hui… En attendant la prochaine chronique, qui sera ma cinquantième, hé oui déjà… Je vous souhaite une excellente semaine ! Et j’attends comme d’habitude vos remarques, commentaires ou suggestions.
  3. 1 point
    Depuis l’explosion de l’épidémie de Covid-19 en Europe, nombreuses sont les initiatives du secteur du numérique qui contribuent à la lutte contre la pandémie ou ses effets. Certains partenaires de Claris (anciennement FileMaker Inc.) ont accepté de travailler bénévolement sur certains projets via l’initiative join::table ou à l’appel de Claris. Chez 1-more-thing, non seulement nous […] Cet article 1app2recover : l’initiative de 1-more-thing pour le déconfinement Covid-19 est apparu en premier sur 1-more-thing. >>> Lire la suite… <<<
  4. 1 point
    Claris a officialisé aujourd’hui la sortie de sa plateforme d’intégration et d’orchestration : Claris Connect. Lors de la DevCon 2020, Brad Freitag (@bradfreitag), CEO de Claris International, annonçait le rachat par Apple/Claris de la startup italienne Stamplay. Quelques mois plus tard, Claris Connect est né ! Cette plateforme permet de créer et d’automatiser des flux […] Cet article Claris Connect : la nouvelle plateforme d’intégration/orchestration est apparu en premier sur 1-more-thing. >>> Lire la suite… <<<
  5. 1 point
    FileMaker Shopify Integration Shopify is used by more than a million businesses in over 175 countries, including Nestle and Staples, making it one of the leading e-commerce companies in the world. By integrating FileMaker and Shopify, you have the ability to easily create, update, and delete nearly all aspects of your online business straight from your FileMaker system. Running Shopify from your existing FileMaker solution can save you time and money by eliminating the pain of double data entry and can keep the two constantly up-to-date. Connecting to Shopify Shopify uses basic authentication, making it incredibly simple to make API calls. The only information you need is the API Key, the API password for your private app, your store’s name (with hyphens instead of spaces), and the specific endpoint for the call that you are trying to make. To retrieve your API Key and password, you simply create a new private app on your Shopify dashboard. The key and password will be automatically generated. Once you have the key and password, using Shopify’s Rest API couldn’t be easier to use. As an example, the call to pull orders would look like this: {API Key}:{API Password}@{Store-Name}.myshopify.com/admin/api/2020-01/orders.json Capabilities The included demo file specifically covers pulling orders from Shopify, but that is just the tip of the iceberg. Shopify’s API has endpoints for pretty much any type of call you would ever want to make. From creating or updating customers, to creating products, to pulling order information from a given date range, integrating with Shopify can handle just about any action you’d want to take straight from FileMaker. The API documentation will tell you everything you need to know for each call you are trying to make. It even shows you any query parameters that can be added to your call to receive more specific information. For instance, you can append the created_at_min query parameter to show all orders created at or after a specific time. Shopify measures time by UTC, so be sure to include your UTC offset at the end of the call so that the time that you’re attempting to query is relevant to you. Ours is -5:00. {API Key}:{API Password}@{Store-Name}.myshopify.com/admin/api/2020-01/orders.json?created_at_min=2020-02-05T15:00:-5:00 Shopify’s API will also give great examples of the response information that you will receive from a successful call. With the JSON that you receive from your request to Shopify, you can store the data into a field or variable and then use FileMaker’s JSONGetElement function to pull JSON values using the JSON keys. Conclusion Integrating FileMaker with Shopify is not only incredibly simple, but incredibly powerful. With basic calls you will be creating products, updating orders, and keeping track of billing, all from your FileMaker system in no time. Contact us if you would like help integrating your FileMaker application with Shopify! Did you know we are an authorized reseller for FileMaker Licensing? Contact us to discuss upgrading your FileMaker software. Download the FileMaker Shopify Integration Database Please complete the form below to download your FREE FileMaker database file. Name* First Last Company Phone* Email* FileMaker Experience*New to FileMaker Platform Existing User of FileMaker Existing Developer of FileMaker Terms of Use I agree OPT-IN: I agree that I am downloading a completely free FileMaker application file with no strings attached. This database is unlocked, and I may use it for my business or organization as I see fit. Because I am downloading a free database, I agree that I should receive occasional marketing. I understand that I can OPT-OUT of these emails at anytime. Constant1 Afficher la totalité du billet
  6. 1 point
    Photo by Plush Design StudioCreating more gender-inclusive solutions Where we discuss what simple things can be done in an application or database to improve gender inclusivity. As a FileMaker developer, I create databases that are designed to store various kinds of data on a daily basis, for a lot of clients in very different fields of work ; one of the most common modules I usually develop is a “Contacts” module, where my clients can enter the info they have on their own clients, for example. Usually, between the classic “First name”, “Last name” or “e-mail address” fields, I just add a “Gender” field, and a simple value list, “Mr / Mrs”, and leave it like that. However, on a recent project, I wanted to change a little thing — nothing too fancy — and added a “Non-binary” value to the value list. But as soon as the client got access to the database, they removed the “Non-binary” option. Meh, their application, their rules, I guess. This annoyed me a little ; so, in order to get a small revenge on life, the universe and everything, I decided to write a small article on gender inclusion in the applications that we develop. Here goes! (Note: this article is written in English, but includes some references to specific French possibilities, as it is my first language. Also, the given examples are created in FileMaker, as it is the technology that I use in my job, but everything that you see in screenshots can be applied to any technology.) About gender forms Before even starting to create a “gender” field, ask yourself: is this info important to your database, and what it will add to your business? After all, you don’t need to know a client’s gender to invoice them, for example. If you don’t have that field in your database, you can avoid the following considerations all-together. So, if we want to enter someone’s gender in a database, we can start by adding “Man / Woman” or “Mr / Mrs” in a value list, right? Well, first, “Mr” and “Mrs” are more titles than genders, but we can indeed start here. The label next to our field can then be “Title” instead ; if it is not clear enough for you, keep “Gender”, but avoid things like “Sex”, as sex and gender are not the same at all — one being biological, the other a social construct. And the other values? You can add “Neutral” in order to avoid having only the 2 previous values — or “Mx” as a neutral equivalent to “Mr” and “Mrs” — but people might still need other options. If you don’t want a long list of items that can be harder and harder to maintain and may be misinterpreted, you can add another field next to it, a “custom” field, where people can enter their preferred gender in a free text. And is knowing the gender of one of your contacts that important to you? Should it really be a mandatory field? If you don’t need it that much, make it optional, by adding a “prefer not to answer” value in your value list for example. A free text field is shown if the user chooses the value “Custom”Speaking of other values, some have to be avoided, like “miss”: you are asking a person’s gender, not if they are married or not. Also, I don’t know what is the position on the “miss” word in English, but friendly reminder that “Mademoiselle” is forbidden in official French documents since 2012… Other values to avoid are job titles ; if you need to send an e-mail and want to start by “Dear Mr / Mrs / Doctor / Colleague”, try to have a separated field for that — you can have an auto-enter option on this field depending on the selected gender to save time. A doctor still has a gender, and there isn’t supposed to be a hierarchy where doctors are above gender. Finally, even if it starts with a good intention, try to avoid putting the value “Other” as a possible gender, as it can be seen as pejorative and too general. The title is separated from the gender (with a visualisation of the final text next to it)Are you proud of your form, now? Well, let’s change everything then! Asking for a gender is nice, but asking for pronouns is better, as it tends to be easier to answer. Don’t worry, there is not a lot to modify: replace “Mr” by “He/him/his”, “Mrs” by “She/her/hers”, and “Mx” by “They/their/theirs” — “They” being more and more used as a neutral equivalent to “He/she”, and not just for the 3rd person of plural. In French, the equivalent that is also being more and more used is “iel”, neutral equivalent of “il/elle”. The “Gender” is replaced by “Pronouns”You can of course find other ways of creating gender forms ; for example, by using checkbox sets instead of asking the user to choose only one option. And maybe think of other original kinds of forms! But what about GDPR? YES, what about GDPR? Don’t forget, gender is of course considered as personal data, and then falls under the GDPR (General Data Protection Regulation, asking you to store personal data only if you can justify how you will use it)! Once again, ask yourself if you really have a valid reason to store the gender of your contacts ; if not, then you are not supposed to store this info. And if you do store it, then, like for any other personal data, inform your contacts in which way the info about their gender is going to be used. For better security, be sure to give access to personal data only to the people that are going to use it. Not everyone in your company that is going to use your database should have access to it, just the people that will, for example, use the gender to generate headers for an e-mail campaign (“Dear Mr/Mrs/Mx, …”). A small popover indicates the way this personal data will be usedBe sure to stay in a well-defined environment: you can ask for someone’s gender or pronouns, but don’t go too far. For example, don’t put options like “trans woman” or “trans man”, as this is a really personal subject, with very little cases where its use can be justified. Moreover, asking for someone’s sexual orientation is completely off-subject and CANNOT be stored ; following GDPR, this falls under the “highly-sensitive” data, information that can only be stored with a special licence, only given for very specific cases — in other examples, a modeling agency can be delivered a special license to store info about someone’s measurements, skin colour, etc. And in the rest of the application? Indeed, you can improve the gender-inclusion of your application in other parts, and not just in a gender form. For example, in the field that usually comes just after the gender: the first name. You can have 2 fields, one for the “legal” name, and the other for the “preferred” name — but again, think about how to justify it on a GDPR point of view! Concerning jobs/occupations, there is no point in trying to gender them ; even if a job is supposed to be occupied by a majority of men/women in the common imaginary, these views have no room in an application and can often be false, and always condescending! For example, instead of using “barman” or “barmaid”, use “bartender” ; instead of “housewife” or “househusband”, use “housemaker”. These cases are more common in languages like French, where for example the job of “Assistant” takes an “e” when practiced by a woman, “Assistante”. To avoid that, a usage that is progressively getting more attention is “inclusive writing” (“écriture inclusive”), where a separator is used to transform a word and make it more “neutral” — the example would then become: “Assistant·e”. The separator used is often the character “·”, but can virtually be anything that you prefer (“.” / “-” / “( )” / etc). Finally, choices can be made while choosing colours and images & icons: no need to choose blue & pink if your application is supposed to be used by a majority of men or women, and no need to choose clearly gendered characters in your different icons or illustrations. A possible version of a simple “Contacts” module.But what’s the point? More and more people declare that they are not ok with their assigned gender — this does not mean that it is a new phenomenon, but that the world is evolving and starting to accept that the “male/female” division is not the only possible division. All of these suggestions are pretty simple to develop ; a few added fields, one or two more items in a value list, maybe a calculation that regroups everything if you need to make reports or sorts in your application, and a few changes in some labels ; but these small changes can add up to create an application designed for everyone, and create a safe and comfortable space for everyone. Changing mindsets can start with changing small habits ; and if you are not at ease with these topics, then starting to use that kind of forms and interfaces might lead you and others to slowly change of point of view on gender identity. Creating more gender-inclusive applications was originally published in Lesterius on Medium, where people are continuing the conversation by highlighting and responding to this story. Afficher la totalité du billet
  7. 1 point
    Premier jour à la 15ème conférence francophone des développeurs FileMaker, occasion d’être encore un peu nostalgique… Après l’annonce par l’éditeur de reprendre son nom d’origine, Claris, nom qu’il portait lorsque j’ai débuté dans le monde de FileMaker en 1997, me voici de retour sur les lieux de ma première FMconf, au printemps 2006 : Poitiers […] Afficher la totalité du billet
  8. 1 point
    Cet article Des apps personnalisées intégrées à un système central : l’exemple de l’UCLouvain est apparu en premier sur 1-more-thing. >>> Lire la suite… <<<
  9. 1 point
    L’un de nos lecteurs, Martin, partage avec nous un script qu’il a écrit pour réaliser des sauvegardes régulières alors même qu’il n’héberge pas son fichier avec FileMaker Server mais en utilisant la fonction de partage de FileMaker Pro Advanced (partage “pair à pair” accessible depuis le menu Fichier / Partage / Partager avec clients FileMaker…). […] Afficher la totalité du billet
  10. 1 point
    Principe et intérêt d’une fonction personnalisée Lorsqu’on écrit un calcul dans FileMaker, on a une bibliothèque de fonctions assez conséquente dans laquelle nous allons piocher pour combiner différents éléments et aboutir à notre résultat. On peut enrichir cette bibliothèque de deux façons différentes : les plugins les fonctions personnalisées Je vous propose de réaliser une […] Afficher la totalité du billet
×
×
  • Create New...