Copying list item between sites with REST/JSON HTTP Call from Workflow: Why wont these columns copy?

This is a re-post with more information hoping for a better response.

I have 2 lists in a SharePoint site with the following columns:

List 1

  • project ID = Single line of text
  • event type = Choice
  • event desc = Single line of text
  • owning dept = Choice
  • external = Multiple lines of text
  • internal = People and Groups
  • minutes = Multiple lines of text
  • outcome = Multiple lines of text

List 2

  • project status = Choice
  • phase = Choice
  • owner = People and Groups
  • date modified = DateModified

on item creation I want a SharePoint 2013 Workflow to copy the content of these columns to an identical list another site. I have successfully built the HTTP call and the workflow currently creates a new item in the target list with the following columns copied correctly:

  • project ID
  • event desc
  • minutes
  • outcome
  • phase

The other seven columns all return BadRequest when I attempt to add them to the parameters variable. here are some screenshots of my current configuration. enter image description here

enter image description here

enter image description here

enter image description here

Based on this setup, can anyone tell or point me to a resource on how the remaining seven fields should e configured?

How to copy non-text site columns between sites using REST/JSON

I am attempting to set up a SharePoint 2013 workflow which will copy the contents of a list item from a subsite to a logging list on its parent site. I have successfully set up the HTTP web service call and all the single and multi-line text fields in the list copy as intended. The list also has a number of choice fields and user fields but as soon as I add any of these the workflow fails and returns a BadRequest in the log.

how can I get the workflow to pass the contents of my choice and username fields as well? I’m pretty sure the problem is with my Type and Values I’m putting into my parameters dictionary build but I am new to REST/JSON and I don’t know what the fix is.

Experimental design, ” how chatbots can impact on a user’s experience”, is better to use Within subjects or between subjects?

I have to do an experimental design “about how chatbots can impact on a user’s experience when using public transport websites to book journeys”. I am not really sure what type of experimental design to choose, would go for Within subjects or between subjects ?



What’s the difference between a monster that can’t speak and a monster that doesn’t speak?

In their languages section of stats for some monsters, the wording sometimes says “can’t speak” and sometimes says “doesn’t speak.”

What functional difference is there between these two wordings?

Examples of creatures that use the “doesn’t” wording include, Invisible Stalker:

Languages Auran, Understands Common but doesn’t speak it.

Or Pidlwick II from Curse of Strahd:

Languages understands Common but doesn’t speak and can’t read or write

Or, for a more apples to apples comparison (apt, since both the creatures below are plants) :

a Tree Blight:

Languages understands Common and Druidic but doesn’t speak

versus a Twig Blight:

Languages Common understands but can’t speak

How to keep authorization model maintainable on calls between different microservices?

In our environment (as in many others), it is often the case that one microservice must call another in order to accomplish a task.

In our environment, authentication is clear enough – we have a signed JWT containing a list of permissions and roles, as well as a user ID, client ID, and so on.

What we’re less clear on is authorization – ensuring that the authenticated client can (or can’t) do the right stuff, but that the underlying services have all the access they need to do their jobs (even if the client wouldn’t be able to do the same things directly).

We’ve examined a few different options:

  1. Each service does all of its own authorization, and if a privilege escalation is needed, it generates a “God mode” token with an otherwise unchanged payload and a different keypair and makes the call using that. The main concern here is copy/pasted authorization code, and the fact that there’ll be a strong incentive to just always enable God mode when making cross-service calls (which makes it somewhat redundant).
  2. Each service does all of its own authorization, and just forwards the user’s token if it needs to make a call. The concern here is code duplication like in option 1, and also the fact that this is likely to cause a complex interdependent web of permissions that imply other permissions that imply other permissions that… (ad nauseam), creating a maintenance headache as the number of services grows.
  3. A lightweight API gateway service that does “simple” authorization (nothing more advanced than “is this client allowed to use this endpoint at all?”), attaches a user object to the payload, and leaves more specific behaviours to the underlying services, which accept any call as being authorized out of the gate. The major concern with this option is performance and stability – the API gateway service creates a single point of failure that can make the entire system inaccessible if it malfunctions, plus creating a frequently-changing dependency for every service.

The question here is twofold:

  1. Are there any additional pitfalls to the three patterns described above that we haven’t considered?
  2. Which of these is the most common in the wild?

Note that this question is not about service mesh offerings like Istio, as we consider them to be somewhat orthogonal to this issue.

Terminology: Difference between decision variables, features and attributes?

Could there be a difference between the words “feature”, “attribute”, and “decision variable” when used in the same paper? The one I am specifically thinking about is about an optimization method for clustering, but I am also wondering if there generally are any scenarios for which it could be.

I can’t manage to google up an answer that either confirms or denies that these are the same thing, and I have no formal training in data science.

Calculate Meant Time Between Failures ( SRE Metrics) in Java Stack

We are currently trying to capture / calculate Mean Time Between Failures for all our services running in production. We use K8s and Prometheus to monitor the same. MBTR = Total Uptime / Number of failures How to get total uptime in prometheus ? Is it possible to use JVM Metrics , is it a good idea to use ps -eo ? Also how to get number of failures ?

Difference between EffectiveInformationRightsManagementSettings and InformationRightsManagementSettings

Microsoft.SharePoint.Client.File has above two properties. Can someone tell me details about them and difference between them.

According to my research, when IRM on a library is enabled, the details come in EffectiveInformationRightsManagementSettings but then what is the other one used for?

Difference between ‘modify’ and ‘edit’ buttons

Is there a difference between the words ‘modify’ and ‘edit’? I am creating a form that will allow users to make changes to their order – what should the call to action button name be – ‘edit your order’ or ‘modify your order’. Is there any difference in the user expectations when they see either of the two names? Please let me know your thoughts.