Is there a way to package Organization-Wide Addresses in Salesforce? I don't believe I see any related selection in the drop-down list when I look to package.
No. The Metadata Coverage Report is the source of truth for packageability; it shows that the OrgWideEmailAddress entity is not supported in any type of packaging or in Change Sets.
Related
...I'm using the Mule Salesforce connector (for Mule Runtime 4.4.2) in Anypoint Studio (7.4.2).
The Salesforce query language does not allow the * operator to gather all keys from an object, so I'm looking for another means to retrieve a sample object and create a model record that I could use for updates and creation.
Using the Task object (documented here: https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_task.htm) as an example, I find that the describeLayout() and retrieve() methods look promising.
However, when I try to invoke retrieve(), I'm required to submit a list of fields to retrieve.
I don't see the describeLayout() method exposed in the connector, so I haven't seen what it returns.
Have I missed a general purpose approach to allow me to gather every field from a sample object?
[edited for clarity]
See if there's describe support. describeLayout is primarily used if you need to recreate a SF page in a mobile app for example, won't tell you much about field types and will list only fields the end user can see, there can be more hidden in the background.
You could have some luck with REST API describe: https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/dome_sobject_describe.htm
Or metadata API: https://developer.salesforce.com/docs/atlas.en-us.api.meta/api/sforce_api_calls_describesobjects_describesobjectresult.htm
I don't know what's available for you. I'd expect Mule connector to do it for you as part of some connection wizard, pull info about all queryable tables and after you pick one - about all fields you can see in it. Maybe you're overcomplicating something, you need a truly dynamic SELECT * equivalent, that would work when admin adds new fields without having to refresh the connection?
Metadata can also be queried, it's stored in tables like actual data. See if https://stackoverflow.com/a/60067076/313628 helps.
...so it turns out that the Mule 4 Salesforce connector does support describe SObject.
To the Anypoint Studio developer, it shows up like this:
The XML definition offers little further insight.
Update: After further investigation, it turns out that an additional operation needs to be applied using Dataweave to get a simple list of fields. After you have the SObject structure in payload, you will:
payload.fields.*name
This yields an array with the field names.
Doing some discovery with commercetools. I notice that in the Rest JSON message when fetching a product, there is an element : catalog. It looks to be an array. But I have not found anything in the documentation that indicates if there is an ability to have say different catalogs for a given application - For example a Master / Child catalog structure.
So the question is - is there such a thing within this tool? And if so, how would one go about setting it up.
Yes, there is a structural element in the product master data that is a catalog-like concept. It is not implemented as a feature with behavior thoug and the current development plans are not intending to activate this structure for multi-catalog / multi-market / multi-XYZ cases.
But there are ongoing development activities to improve support for such requirements in in a different way. You best watch the release notes to stay up to date.
The Enterprise Architect keeps the connections of a Graph in the Database.
I am looking for a way to export the information flows of a Diagram.
For this purpose i would need to sets of simple outputs:
A Matrix-View where the Names of the Elements are the X, Y-Axis and an X is drawn where they intersect
A List-View where all Information Flows are listed with their source and sinks.
I tried using a report, but i just could not get this to work for me.
It sounds like you're taking slightly the wrong approach here.
In Enterprise Architect, a diagram is not a container of information. It is a display which shows a selection of information from the underlying data store. This is in stark contrast with drawing tools, like MS Visio.
The EA data store is organized into packages, and that shows through the entire product. So if you edit an RTF document template, for instance, you will note that the internal template structure is based on a package structure -- it doesn't start from a diagram. You will also note that the context menu for a package or an element contains a Documentation sub-menu, but there isn't one in the diagram context menu. Same reason; a diagram is not a starting point for a document.
Now that said, you can create an RTF template which outputs only the information flows to/from the elements included in the generation scope, but you need to start off from a package and create your template based on a package structure. Setting up a table in a template is a little fiddly the first time but it's not impossible. In order to select only the information flows, use the Exclude Filters tab in the Generate Documentation dialog to exclude all connector types except Information Flow.
The matrix view you're looking for is known as a Relationship Matrix, located in the View menu (in EA 11.1). Again, it's based on a package structure, not a diagram structure. Relationship matrices can be included in generated documents as well.
I'm developing a Salesforce package that depends on some prepopulated data to work correctly (ie: a list of countries to populate a custom setting).
Is there a way to prepopulate these objects at installation/upgrade time? (e.g. uploading a csv with the data I need to insert into some custom objects).
Is there a way to run a custom script at installation/upgrade time? (e.g. have the script update information on new fields, or adapt existing data to a modified object structure).
Thanks in advance.
This is actually a new piece of functionality that is coming in the Summer '12 (API Version 25.0) release. There are two new interfaces to implement, InstallHandler and UninstallHandler, which can be setup to run on install and uninstall of a package respectively. You could implement the InstallHandler and populate the objects/custom settings in that class.
An alternative is to use a custom settings value to know if the installation procedure was run. Then you can use your package's point of entry to check for it and do the procedure if the value indicates it needs to run. It's a little complicated if you don't have a single point of entry.
I was wondering if there's a way to export package information from Cognos 8 from a regular user level or from the framework level.
For instance, I want the field names that cognos is pointing to on the database, i want the datatype, the description cognos uses when you right click a data element, etc..
Any suggestions?
(Unfortunately I'm not at my work computer right now) but Cognos saves everything in .xml files. I have an xml pretty printer that I use on model.xml before and after edits, so that I can use windiff to see what exactly changes in the model. I have also used an xml editor on model.xml on several occasions for global search and replace.
Having said that, I'm not sure how much of the database schema you can infer directly from model.xml, but I suspect if you had a script that could read and walk model.xml, and connect to the database to describe the objects, you could get what you need.
The answer appears to be yes, to anything that supports CWM (the Common Warehouse Model) but as for how...
One suggestion: ask IBM.
It appears that Powerdesigner 15 imports from xmi models.